Update: (Dec 5, 2010) The Diagnostics page is available on NuGet now. For more information, see Phil Haack's blog post. Since we rev this page with every release of MVC, NuGet is an excellent release vehicle, because it allows you to always have quick access to the latest version.
When we released ASP.NET MVC 2, we included a file in the MvcFutures package (download) called MvcDiagnostics.aspx.
This single WebForms page can be dropped into any MVC site, and then viewed in your browser. It will give you diagnostic information about ASP.NET MVC, which can be very helpful when trying to figure out why your MVC application isn’t working. (It’s a WebForms page because, if MVC is broken for you, what good would an MVC page be? :) )
Two common problems we see on the forums include:
- Version mismatch between MVC and MvcFutures. This will detect that situation and let you know that your versions are mismatched.
- Problems where a site works locally but fails when put into a hosted environment. This usually happens because of mismatched or missing MVC dependencies, both of which this can help you detect.
Don’t be surprised if we ask you to run this page to help us help you diagnose issues with your MVC applications. :)
This utility knows about many versions of MVC, including all the version numbers for MVC since 1.0 Preview 2. Despite the fact that we’ve put it in the MVC 2 Futures download, it can be used to detect problems for both MVC 1.0 and MVC 2 applications.
Here’s what it looks like when I drop it in a new MVC 2 site:
Hope that helps!
