Analysis on making ASP. NET error pages

What is the necessity for creating an ASP. NET error page? After a Web application is published, a custom error page instead of ASP is redirected when an error occurs to give the user a friendly interface and user experience. NET to expose a detailed list of exceptions to users.

Simple ASP. NET error page creation can be set through web. config

The following is a reference clip:

 
 

  
  
﹤customErrors mode="RemoteOnly" defaultRedirect="GenericErrorPage.htm"﹥   
  
  
　﹤error statusCode="403" redirect="NoAccess.htm" /﹥   
  
  
　﹤error statusCode="404" redirect="FileNotFound.htm" /﹥   
  
  
﹤/customErrors﹥  
 
 

To program the cause of an ASP. NET error page, you can use the Page_Error event.

The other method can be implemented through Global. asax. I think this method is more convenient. In addition, if you can combine a separate and more friendly page, it seems more comfortable:

Global. asax (you can record the error log if necessary)

The following is a reference clip:

 
 

  
  
VoidApplication_Error (ObjectSender, EventArgs e)
  
  
{
  
  
Exception objErr = Server. GetLastError (). GetBaseException ();
  
  
　StringError ="Exception page :"+ Request. Url. ToString () +"<Br>";
  
  
Error + ="Exception information :"+ ObjErr. Message +"<Br>";
  
  
Server. ClearError ();
  
  
Application ["Error"] = Error;
  
  
Response. Redirect ("~ /ErrorPage. aspx");
  
  
}
  
  
ErrorPage. aspx
  
  
 
  
  
Protected VoidPage_Load (ObjectSender, EventArgs e)
  
  
{
  
  
ErrorMessageLabel. Text = Application ["Error"]. ToString ();
  
  
}
 
 

When end users use an application, they may not want to know the cause of the error. In this case, we can use the check box to determine whether to display the cause of the ASP. NET error page. You can place the Label in a div and use the check box to determine whether to render the div.

The following is a reference clip:

 
 

  
  
﹤script language="JavaScript" type="text/Javascript"﹥   
  
  
﹤!--   
  
  
function CheckError_onclick() {   
  
  
　var chk = document.getElementById("CheckError");   
  
  
　var divError = document.getElementById("errorMsg");   
  
  
　if(chk.checked)   
  
  
　{   
  
  
divError.style.display = "inline";   
  
  
　}   
  
  
　else   
  
  
　{   
  
  
divError.style.display = "none";   
  
  
　}   
  
  
}   
  
  
 
  
  
// --﹥   
  
  
﹤/script﹥ 
 
 

 

We can make some friendly designs on the errorpage to replace the ASP. NET error page, which makes people look more comfortable.

This article describes how to create an ASP. NET error page.

1. Analysis of Theme functions in ASP. NET development skills
2. Analysis of ASP. NET configuration file format
3. Analysis of ASP. NET Configuration File hierarchy and inheritance
4. Scope of ASP. NET configuration settings
5. Analysis of ASP. NET configuration error page