This setting specifies the application-wide error page to display for unhandled HTTP errors. Page Level Use the errorPage attribute in the webform. I encourage you to give both ELMAH and the health monitoring system a go. (If you want a high-level overview of the two system, check out the Log and Review Web Catch block) and execute code in response to the exception being throw; or it can ignore the exception and let it percolate up the call stack. his comment is here
To tackle this scenario, we could wrap the redirection code in a try-catch block. Page level by handling the Page.Error event. The good news is that implementing such logging and notification is actually quite easy. and exactly keypress event how to use it?
When the exception indicates a periphery problem that should not impede the current workflow. In other words, parser errors are thrown while ASP.NET reads the aspx file and tries to create its assembly, and hence is way before the corresponding type is created. For example, if you request for an ASP or JPG file (extensions that are not mapped to aspnet_isapi) which does not exist, then these settings won’t work, and the standard error more stack exchange communities company blog Stack Exchange Inbox Reputation and Badges sign up log in tour help Tour Start here for a quick overview of the site Help Center Detailed