Remember to always have a static customErrors page

I was just surfing around on http://forums.microsoft.com and got a yellow screen of death!

I must say I was slightly surprised. In web projects that I have been involved in we have always added two customErrors pages one to handle generic errors which redirects to an errorpage.aspx page and then a static html page errorpage.html which is only used when an error occurs on the dynamic error page… A sample configuration using location follows:

<configuration>

<system.web>
 <customErrors mode="on" defaultRedirect="errorpage.aspx"/>
</system.web>

<location path="errorpage.aspx">
 <system.web>
  <customErrors mode="on" defaultRedirect="errorpage.html"/>
 </system.web>
</location>

</configuration>

That way if we have a problem with our application that affects the entire site, for instance menu and navigational rendering, we can still show a nice error page with a message like “The site is temporarily unavailable, please try again in a few minutes.”

Related posts:

1. Strange ASP.NET Web Parts database exception.
2. Finished update to 2.0
3. Running dasBlog as a partially trusted application