CodeKicks.com
Focus on Microsoft Technologies - Tutorials, Articles, Code Samples.

Thursday, September 14, 2006

Working with Custom Error Pages Using ASP.NET

Every application should have error handling.  We try to trap errors using try-catch-finally block.  But what happens in the case of an unhandled exception in application?  ASP.NET produces an error page (usually located at c:\winnt\help\iishelp\common) when an application throws an unhandled exception or when we deploy an .aspx file whose source contains a syntax error without compiling it inside Visual Studio .NET first.  By default, ASP.NET displays error messages that include .NET error description along with a stack trace (see Figure 1).  There is a lot of information in the error message.  The stack trace points out the location where the specific error occurred and the last line informs us about the version used in .NET Framework.  This information is very useful for a developer because it tells why and where the error occurred.  

Find Complete Article on Working with Custom Error Pages Using ASP.NET

Post a Comment