ASP.NET MVC Incoming request does not match any route
Been developing an MVC application over the last month or so and struggled getting the first version installed and running on the client’s web server this week. No problems running locally but refused to run on the web server.
I use NAnt and CC.NET for my integration platform and configured a quick build file for the MVC application, taking a lot of the settings from our .NET 2 projects at work, without giving it much thought. Ran the build and deployed the files – ERROR – Incoming request does not match any route.
I was deploying to IIS6 and no amount of wildcard mappings or .mvc extensions helped.
In the end, turns out my problem was caused by a missing Global.asax file. Sounds simple now but excluding them in .NET 2 projects is never an issue as the application config location is determined from a .compiled file in the bin directory.
Putting the Global.asax stub file back in the website root and all is good in the world again!
3 comments so far
Leave a reply
[...] to VoteASP.NET MVC Incoming request does not match any route (11/14/2008)Friday, November 14, 2008 from timpeel.wordpress.comNET for my integration platform and configured a [...]
I had this exact problem with my first ever ASP.NET MVC application and I finally found this blog post after hours of debugging. Thank you!
You just saved me a lot of time. I had the same problem and fixed it within 2 minutes! Thanks!