title: Serve Static Files outside MVC pipeline
body: <p>I'm attempting to build a single page application using AngularJS on the client side and asp.net with Web API on the backend. I've been utilizing a complex client side build pipeline using Grunt. Long story short, this tool provides me a <code>dist</code> folder which contains all of my scripts/styles etc and is minified, uglified and all that good stuff.</p>
  
  <p>At this point, I have no need for the server side MVC pipeline when it comes to URL routing and view rendering. I've placed the dist package at <code>siteroot/Content/dist</code>. Ultimately, my goal is to statically serve the files located there and leave the rest of the application intact. However, I've found no way to be able to do this. I'm forced to navigate to <code>mysite.com/content/dist</code> in order to actually see my application. I discovered virtual applications and directories and have attempted to remap the application at <code>/</code> to <code>site\wwwroot\Content\dist</code>. This has the intended effect in that now navigating to the root of my site serves the HTML files I'm looking for, however it simultaneously seems to break all of my Web API endpoints as it appears that the application is running out of a different path entirely.</p>
  
  <p>Is there a way that I can have the best of both worlds? I want my API endpoints to exist as they do now but simply serve my site statically out of <code>\Content\dist</code></p>