.NET Routes under IIS6
Tuesday, January 4, 2011
I think I'm going to start making a habit of writing up a post everytime I solve some tricky problem in a manner I'm unlikely to remember the next time said problem shows up. This time, I had created a few .NET Routes to handle uploaded resources in my new web-mail-client. They worked fine in development (with the light-weight webdev application) but failed once I moved the code into production (Windows 2003 Server - IIS6).
Turns out we need to set an additional IIS property:
- In the Web Site's property, configure the Application Settings.
- Under "Wildcard application maps", insert a new mapping.
- Set the "Executable" to the .NET v2.0 DLL: c:\windows\microsoft.net\framework\v2.0.50727\aspnet_isapi.dll
- And uncheck "Verify that file exists".
Custom routes should now work.
Add a Comment