When an error occurs in an application in production, it is important that the developers are notified of the error so that they can unearth the cause of the exception and address it. Using a human-friendly custom error page that matches the look and feel of the site is preferred to the default Runtime Error YSOD, but displaying a custom error page is only one part of a comprehensive error handling solution. In the preceding tutorial we configured the application to use a custom error page for remote users and the Exception Details YSOD for users visiting locally. There are three different types of error pages: the Runtime Error Yellow Screen of Death (YSOD) the Exception Details YSOD and custom error pages. When an unhandled exception occurs in an ASP.NET application, it bubbles up to the ASP.NET runtime, which raises the Error event and displays the appropriate error page. This tutorial provides an overview of how ASP.NET processes runtime errors and looks at one way to have custom code execute whenever an unhandled exception bubbles up to the ASP.NET runtime. When a runtime error occurs on a web application in production it is important to notify a developer and to log the error so that it may be diagnosed at a later point in time. View or download sample code ( how to download)
0 Comments
Leave a Reply. |