I am currently deploying my application built using RC of MVC ASP.NET on the production server which is showing nothing now. The routes in my global.ascx are typical i.e. <
Justin case that anyone is hitting the same issue as I had, try to monitor:
protected void Application_Error(object sender, EventArgs e) {
For me the application was failing silently and I did not know, so obviously it was returning a blank, but the confusing part was returning a 200 as http response status code.
Anyhow, I hope this helps someone in the future.
Try deleting the app_offline.htm
file if it is being created in your Application.
From the looks of it I would expect that the first route would work if you were going to a url like /Home.aspx but if you are just going to the / url then ASP.net does not know how to handle the URL. It will try and match on IIS defaults pages like index.html, default.aspx, index.aspx, etc. If nothing is found then the request isn't getting anywhere. Trying creating a default.aspx (or any other index file in the route), then in the page_load do a response.redirect("~/Home.aspx")
.
If that doesn't work I would check out this source. One of the main reasons IIS 6 and MVC don't play nice is that IIS 6 by default does not have the wild card * mapped to the ASP.net dll.
I am sure it is a way that the product server is configured, can you do any comparison between your XP instance and production?
The blank page is shown when errors occur in particular places - in my case it was a MethodNotFoundException...
To see the error, make sure you enable "HTTP Errors" and "HTTP Redirection" services in the "Web Server (IIS) role.
Normally when I get this, it's because I've forgotten to add the following into the Web.config when deploying to IIS6 after developing on IIS7 (or the IIS Express 7 that comes with Visual Studio):
<system.webServer>
<modules runAllManagedModulesForAllRequests="true" />
</system.webServer>
What's the server environment? If it's not IIS7/Server 2008 there are other tweaks you have to do to get the routing to work correctly, although if that's the case you would probably get an error page, not a blank page.