Share via


Exceptions

When an ASP.NET application encounters an unhandled exception or other error while processing a request, it generates an error page; however, many mobile devices cannot render the detailed contents of an error page. Instead, such devices usually show only a device-specific error message, or the error code. To address this situation, ASP.NET mobile Web Forms pages try to format the error page to render on the device.

Device-specific rendering is limited to exceptions that occur while running the page; therefore, if you use default error pages, try out your mobile Web Forms pages first on a desktop browser to detect configuration or compilation errors.

You can configure your application to generate default or custom error pages. Default error pages set an error code in the response and display a page to describe the error in detail. However, you can create custom error pages for deployment that are less complex and contain only information that is useful to the end user. A typical custom error page might contain information like a telephone number for contacting your customer support team.

Setting various exceptions in Visual Studio Team System