Error Trapping Asp.net
Working with Multiple Environments Hosting Managing Application State Servers Request Features Open Web Interface for .NET (OWIN) Choosing the Right .NET For You on the Server MVC Testing Working with Data Client-Side Development Mobile Publishing and Deployment Guidance for Hosting Providers Security Performance Migration API Contribute ASP.NET Docs » Fundamentals » Error Handling Edit on GitHub Warning This page documents version 1.0.0-rc1 and has not yet been updated for version 1.0.0 Error Handling¶ By Steve Smith When errors occur in your ASP.NET app, you can handle them in a variety of ways, as described in this article. Sections Configuring an Exception Handling Page Using the Developer Exception Page Configuring Status Code Pages Limitations of Exception Handling During Client-Server Interaction Server Exception Handling Startup Exception Handling ASP.NET MVC Error Handling View or download sample code Configuring an Exception Handling Page¶ You configure the pipeline for each request in the Startup class's Configure() method (learn more about Application Startup). You can add a simple exception page, meant only for use during development, very easily. All that's required is to add a dependency on Microsoft.AspNetCore.Diagnostics to the project and then add one line to Configure() in Startup.cs: public void Configure(IApplicationBuilder app, IHostingEnvironment env) { app.UseIISPlatformHandler(); if (env.IsDevelopment()) { app.UseDeveloperExceptionPage(); } The above code includes a check to ensure the environment is development before adding the call to UseDeveloperExceptionPage. This is a good practice, since you typically do not want to share detailed exception information about your application publicly while it is in production. Learn more about configuring environments. The sample application includes a simple mechanism for creating an exception: public static void HomePage(IApplicationBuilder
resources Windows Server 2012 resources Programs MSDN subscriptions Overview Benefits Administrators Students Microsoft Imagine Microsoft Student Partners ISV Startups TechRewards Events Community Magazine Forums Blogs Channel 9 Documentation APIs and reference Dev centers Retired content Samples We’re sorry. The content you requested has been removed. You’ll be auto redirected in 1 second. MSDN Library MSDN Library MSDN Library MSDN Library Design Tools Development Tools https://docs.asp.net/en/latest/fundamentals/error-handling.html and Languages Mobile and Embedded Development .NET Development Office development Online Services Open Specifications patterns & practices Servers and Enterprise Development Speech Technologies Web Development Windows Desktop App Development TOC Collapse the table of content Expand the table of content This documentation is archived and is not being https://msdn.microsoft.com/en-us/library/bb397417.aspx maintained. This documentation is archived and is not being maintained. Complete Example for Error Handlers Other Versions Visual Studio 2010 .NET Framework 4 Visual Studio 2008 This code example includes elements for both page-level and application-level exception handling. Code Example Files The example consists of the following files: Web.config Global.asax Default.aspx ExceptionUtility (to be put in the App_Code folder) GenericErrorPage.aspx HttpErrorPage.aspx Http404ErrorPage.aspx DefaultRedirectErrorPage.aspx Web.config The following example shows the Web.config file. The customErrors section specifies how to handle errors that occur with file types that are mapped to ASP.NET, such as .aspx, .asmx, and .ashx files. (In IIS 6.0 and in IIS 7.0 in classic mode, static content files such as .html and .jpg files are not mapped to ASP.NET.) The settings in the example customErrors section cause any unhandled HTTP 404 (file not found) errors to be directed to the Http404ErrorPage.
resources Windows Server 2012 resources Programs MSDN subscriptions Overview Benefits Administrators Students Microsoft Imagine Microsoft Student Partners ISV Startups TechRewards Events Community Magazine Forums Blogs Channel 9 Documentation APIs and reference Dev centers Retired https://msdn.microsoft.com/en-us/library/w16865z6.aspx content Samples We’re sorry. The content you requested has been removed. You’ll be https://msdn.microsoft.com/en-us/library/aa479319.aspx auto redirected in 1 second. MSDN Library MSDN Library MSDN Library MSDN Library Design Tools Development Tools and Languages Mobile and Embedded Development .NET Development Office development Online Services Open Specifications patterns & practices Servers and Enterprise Development Speech Technologies Web Development Windows Desktop App Development TOC Collapse the table of content error trapping Expand the table of content This documentation is archived and is not being maintained. This documentation is archived and is not being maintained. Error Handling in ASP.NET Pages and Applications Other Versions Visual Studio 2010 .NET Framework 4 Visual Studio 2008 .NET Framework 3.0 Visual Studio 2005 This section describes how to check for errors in your pages and create global error handlers. In This Section error trapping asp.net How to: Handle Page-Level Errors Provides information about how to catch unhandled errors in the code for the page on which they occur. How to: Handle Application-Level Errors Provides information about how to catch unhandled errors that occur in any page in the Web site. Related Sections ASP.NET Troubleshooting and Debugging Provides information about techniques for how to find errors in ASP.NET Web applications. How to: Display Safe Error Messages Provides information about security implications of displaying error messages. See Also Other Resources Rich Custom Error Handling with ASP.NET Show: Inherited Protected Print Export (0) Print Export (0) Share IN THIS ARTICLE Is this page helpful? Yes No Additional feedback? 1500 characters remaining Submit Skip this Thank you! We appreciate your feedback. Dev centers Windows Office Visual Studio Microsoft Azure More... Learning resources Microsoft Virtual Academy Channel 9 MSDN Magazine Community Forums Blogs Codeplex Support Self support Programs BizSpark (for startups) Microsoft Imagine (for students) United States (English) Newsletter Privacy & cookies Terms of use Trademarks © 2016 Microsoft © 2016 Microsoft
resources Windows Server 2012 resources Programs MSDN subscriptions Overview Benefits Administrators Students Microsoft Imagine Microsoft Student Partners ISV Startups TechRewards Events Community Magazine Forums Blogs Channel 9 Documentation APIs and reference Dev centers Retired content Samples We’re sorry. The content you requested has been removed. You’ll be auto redirected in 1 second. Web Applications (ASP.NET) ASP.NET Infrastructure Infrastructure Rich Custom Error Handling with ASP.NET Rich Custom Error Handling with ASP.NET Rich Custom Error Handling with ASP.NET The ASP.NET HTTP Runtime The ASP.NET Page Object Model ASP.NET Performance Monitoring, and When to Alert Administrators E Pluriblog Unum: Merging RSS Feeds Enterprise Localization Toolkit Finite State Machines, Wizards and the Web Globalization Architecture for ASP.NET One Site, Many Faces The Quest for ASP.NET Scalability Regular Expressions in ASP.NET Rich Custom Error Handling with ASP.NET Search Dynamically for Plug-Ins skmFAQs.NET: An ASP.NET FAQ Application Turn Your Log Files into Searchable Data Using Regex and the XML Classes Understanding ASP.NET View State Using Visual SourceSafe for ASP.NET--Start to Finish Walkthrough: Tracking Server Progress from an ASP.NET Client Application Watching Your Server Processes TOC Collapse the table of content Expand the table of content This documentation is archived and is not being maintained. This documentation is archived and is not being maintained. Rich Custom Error Handling with ASP.NET By Eli Robillard January 2004 Applies to: Microsoft® ASP.NET Summary: Adding your own custom error handling to your ASP.NET Web applications can ease debugging and improve customer satisfaction. Eli Robillard shows how you can create an error-handling mechanism that shows a friendly face to customers and still provides the detailed technical information developers will need. (19 printed page