¿Handling Errors?

Daniel Infante

What should I use to handle errors on a page?

options :

- Web.config - Global.asax 
- Default.aspx 
- ExceptionUtility 
- GenericErrorPage.aspx
- HttpErrorPage.aspx 
- Custom Errors

7 Replies

Know the answer? Post it — somebody with the same question will find it here.

Praveen Dhatrika11y ago
for custom errors click below
http://csharp-video-tutorials.blogspot.com/2012/12/custom-errors-in-aspnet-part-71.html

And the good practice is, Never show the yellow screen of death(error message) to the end user, instead redirect him to a page that says, "Site under construction/ or please try after some time, Unable to retrieve", and also use the Log tools like Log4net, Elmah. where you can catch exception and log them somewhere so we can trace later looking at error mesages
Daniel Infante11y ago
Thank you.
I had planned to use log4net , but what's the difference with " CustomError " and / or options that gave me .
What is good practice?
Praveen Dhatrika11y ago
first option, would say catch the exception and log the details and then redirect the user to an error page that says "the site is under construction, sorry for inconvenience"

So, to publish my project (in production) , which is recommended.

Praveen Dhatrika11y ago
It always the best practice to catch the exceptions and log the details to the developers team and also show user an error page that actually describes that It takes some time, instead of showing the error description to the user. The best practice is using try-catch or there are some logging tools that automatically catches exceptions and throw them to desired error page. As I say the second option, I said to use Custom error pages provide the flexibility of displaying a specific page in response to one or more of the available HTTP status codes. For a list of all the available HTTP status please visit the following Article. http://en.wikipedia.org/wiki/List_of_HTTP_status_codes

Why do you recommend those options to control my mistakes on my website ? 
More details, please .  
Thank you.

Praveen Dhatrika11y ago
Error page(using try catch and redirecting to error page described in web.config) or next option is customerror