Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>I hope the continuation of this thread conveys a willingness to make sure this problem doesn't drive anyone off the cliff. There's a lot of documentation in various forums about solving this issue on Vista but I couldn't find any likewise articles for 2K8. As indicated in this <a href="http://forums.iis.net/p/1143592/1849083.aspx#1849083" rel="nofollow noreferrer">forum post</a> I was able to fix the issue on a Vista machine. Alas, a like execution failed to resolve the matter on 2K8. </p> <p>I had verified that the StaticFileHandler had been included in the web.config <a href="http://www.apijunkie.com/APIJunkie/blog/post/2007/11/Breaking-changes-in-ASPNet-20-HTTP-Handlers-when-moving-from-IIS5-on-Windows-2000-to-IIS6-on-Windows-2003.aspx" rel="nofollow noreferrer">as suggested in this blog post at apijunkie.com</a>. Still, no luck. </p> <p>Clarifying <em>no luck, here</em> - My server-side functionality was perfect. All MVC routes work like a champ. Just all CSS and JS rendering failed. When browser pointed directly at CSS or JS files resulting page was an ASP.NET 404 and not the <em>traditional</em> 404 error page. </p> <p>So I went into the IIS7 Manager and into the Handler Mappings dialog. I added a new handler that specified the System.Web.StaticFileHandler type and gave it an extension of *.CSS. Then I repeated that for *.JS, *.PNG, and *.GIF files. When I refreshed the site in the browser, everything rendered perectly. The screen shots below demonstrate this process. </p> <p>The Handler Mappings Window: </p> <p><img src="https://bradygstorage.blob.core.windows.net/images/managed-handler.png" alt="handler mappings"></p> <p>Adding a new Managed Handler</p> <p><img src="https://bradygstorage.blob.core.windows.net/images/add-managed-handler.png" alt="alt text"></p> <p>This resolved the problem, and now I have a perfectly functioning MVC app hosted in W2K. Time for a Guinness. </p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload