Resolving Issues with IE10/11 HTML5 Video on Windows 7

Recently I encountered an issue on a project where html5 videos that had been working fine were having playback problems on Windows 7 systems in Internet Explorer 10. Further testing showed that IE11 had the same issue as well. Some time on the search engines found others with issues but no solutions.

In the end I was able to trace the issue back to the content types or mime-types that were being assigned to the files when they were being upload to Azure blob storage. I discovered that while videos with the mimetype of “video/mp4″ played fine, other that had been labeled as “Video/mp4″ would not play. The difference being the upper case V. Windows 8 running IE 10 and IE 11 seem to have no problem with this, but something in the Win7/IE10 combination has issues. (IE9 seemed to work fine). From what I could tell, according to RFC 2045 the standard that appears to document content types, case should not matter:

"The type, subtype, and parameter names are not case sensitive.  For
   example, TEXT, Text, and TeXt are all equivalent top-level media types."

Oddly, in the end it did matter. Hopefully if you’re searching for Internet Explorer 10 HTML5 video playback issues on Windows 7 you’ll find this solution sooner than I did.



Who Moved My SPA? (Single Page Application Template)

If you’ve downloaded and installed the latest ASP.NET MVC 4 RC bits, you might have
noticed one of the recently added MVC4 project templates is not longer there. The
Single Page Application (SPA) project template that shipped with the ASP.NET MVC 4
Beta as an early preview, will not ship with the final MVC 4 release. It will however
continue to evolve outside of the MVC 4 release.


More information is available on the ASP.NET
SPA Home Page

“An official release of ASP.NET SPA won’t be ready in time to ship with the final
ASP.NET MVC 4 release.
You can find the source code for ASP.NET SPA and follow
the development effort on the ASP.NET CodePlex site.”

If you look closely you will also notice another change. While it appears that a new
“Basic” template has been added, the previous “Empty” template has been renamed to
“Basic” and a new, much more empty “Empty” template has been added to give a bare
bones empty starting point for an MVC4 project.



After spending some time scouring the web researching some aspects of the ASP.Net
Web API I gathered the following collection of useful links and decided to share them

for the MVC Guy

and consuming REST services with ASP.NET Web API using MediaTypeFormatter and OData

errors and error detail policy in ASP.NET Web API Jimmy

Web API- How content negotiation works

Web API- Extending content negotiation with new formats

& Atom MediaTypeFormatter for ASP.NET WebAPI

With the ASP.NET Web API

download of file from ASP.NET WebAPI

Authorise WebApi with HttpClient

[RequireHttps] with ASP.NET Web API

throttling in ASP.NET Web API


patterns & practices: Project Silk

A team from Microsoft Patterns & Practices have been working to create guidance
for building “Modern Web Applications” in conjunction with an advisory group of individuals
from the developer community.

“Project Silk provides guidance for building cross-browser web applications
with a focus on client-side interactivity. These applications take advantage of the
latest web standards like HTML5, CSS3 and ECMAScript 5 along with modern web technologies
such as jQuery, Internet Explorer 9, and ASP.NET MVC3.”

To achieve this, the team is creating a reference application to give them a real
world example to build and provide a sample to learn from.

The sample application and related guidance documentation are currently available
at and
are free to download. The latest update was June 3rd, 2010 with Drop 10, and updates
will continue to be made as the project continues.

I will be posting more on some specifics of the code and guidance, but wanted to share
this initial post.