When working on modern web applications that use features that are recently supported by browsers such as SVG, you may find that images do not render correctly, or at all in the browser.
When most of use develop and test web applications locally, we use the built-in web server, called ASP.NET Development Server/10.0.0.0. This works fine for testing, and most applications will eventually get deployed to a web server running IIS 7.0 or later.
The ASP.NET Development Server is not aware that it should serve SVG with a MIME content-type of
image/svg. Instead it uses the generic
application/octet-stream. A modern web browser on the other hand will typically either request
image/* or explicitly request
image/svg+xml. If the response is
application/octet-stream, it will ignore the response (tested in IE9, FF14).
The usual way of fixing this is to add this code block to web.config:
Unfortunately ASP.NET Development Server is unable to understand this directive.
To workaround this problem, install and use IIS 7.5 Express to serve the content locally. This will require instructing Visual Studio to use IIS instead.