| | .net101: ASP.NET Error Handling Support |
 | | Instead, in the event that an unhandled error occurs during the processing of a request, you want to be able to display your own "custom error page" that displays your own branding and whatever particular error message you want. |
 | | One thing that we've encountered with custom error pages is that, while they are very useful for production scenarios, they can often be a pain to deal with during development (since you expect to have bugs in development, and really want to see the actual error message trace when you find them). |
 | | While displaying custom error messages to customers is always a good thing -- you also want to make sure that developers and administrators can easily find out (in real time) when an error is occurring on a site, and identify what the problem is (what is the url and the exception information). |
| www.dotnet101.com /articles/art015_errorHandling.asp (1297 words) |