Common Exception Handling and web. config Configuration Analysis in ASP. NET project development

In ASP. NET project development, application exception handling is mainly at the page and method layers. We will separate the descriptions:

◆ Page-level Exception Handling

In addition to writing the processing code in Global. asax, we can also write the code in Page_Error on the page:

 
 

  
  
public void Page_Error(object sender, EventArgs e)  
  
  
 
  
  
{  
  
  
 
  
  
 //Insert same code that is in the Application_Error event.  
  
  
 
  
  
} 
 
 

If an error occurs on the page, the code above will be executed. We can copy all the Code previously written in the Application_Error event to the Page_Error processing method. However, in this case, the code in Application_Error will not run, because the exception is already handled in the previous section, that is, Page_Error.

◆ Method-level processing

I believe that everyone is very familiar with this, that is, the use of common try... catch... finally statement blocks. I will not go into details here.

In ASP. NET project development, how does one implement the web. config configuration?

◆ Web. config Configuration

The exception is usually configured in the web. config file. Node:

 
 

  
  
   "RemoteOnly"     
  
  
 
  
  
defaultRedirect="ErrorPage.aspx">  
  
  
 
  
  
    "403"  redirect= "NoAccess.htm"  />   
  
  
   
  
  
   "404"  redirect= "FileNotFound.htm"  />   
  
  
   
  
  
 
 
 

You should be familiar with some attributes in the node.

In ASP. NET project development, we will introduce you to common exception handling and basic web. config configurations, and hope to help you.

1. Application of ASP. NET trace in page execution
2. Introduction to ASP. NET Request Object Attributes
3. Analysis on adding watermarks to Images Using ASP. NET (VB)
4. Introduction to ASP. NET page framework
5. Analysis of Application Exception Handling in ASP. NET project development