Am pulling my hair out over this!
I have an ASP.NET MVC 2 web application, which up until yesterday was working fine on the hosted server (running IIS 7.5, I don't have direct access to IIS, just web portal access to some features).
Yesterday I attempted to install the ELMAH logging framework (see this article) and now all my routes appear to be hosed. If I access the root at www.mysite.com then the homepage comes up fine, but accessing any route at all (there are 30 or so custom routes added to the table) gives me a 404.
The only things that have changed are:
referencing the ELMAH assembly and copying it to the /bin folder
httpmodules/handlers in both the system.web and system.webserver sections
the elmah config section in web.config
adding the HandleErrorWithELMAH attribute to my base controller from here
I've since reverted all of those changes - commenting out the attribute from the base controller, removing all the ELMAH stuff from the web.config. But it's still not working, which makes me think I've broken something inadvertently in the process.
Any ideas of what else I can try?!
I'm pretty sure that RegisterRoutes is getting called successfully as I stuck a quick throw Exception at the end of the method, which broke the homepage on an app restart, as expected.
I'm set to use ASP.NET 4.0 (Integrated Pipeline).
Any help or ideas much appreciated!