I feel it is better to use the codebehind pages for all aspx pages.
The steps are ok, but what if the error occures while storing errror info into the log table of the database?
means you need to take care when error occors inside the catch/final blocks.
----- Original Message ----
From: " rherrmann05%40comcast.net">rherrmann05
comcast.net" < rherrmann05%40comcast.net">rherrmann05comcast.net>
To: AspNetAnyQuestionIsOk%40yahoogroups.com">AspNetAnyQuestionIsOkyahoogroups.com
Sent: Wednesday, 24 October, 2007 7:31:13 PM
Subject: [AspNetAnyQuestionIsOk] Error handling for an ASP.Net 2.0 web site
Hi all,
I have done only limited error / exception handling in the past. I have used Try, Catch, Finally to catch errors for a specific piece of code. But now I need to capture all errors that can happen in our web site. I want to do the following:
1. Notify the user that an error occured. A generic error web page would be best.
2. Give instructions to the user on how to proceed. Again, a generic error web page.
3. Capture all necessary technical detail and notify our Help Desk that an error occured.
4. Insert a row into our custom SQL table named LogSystem.
Like I said, I know how to use Try / Catch. But do I have to use this in the code behind of every web page? Is it possible to capture all errors even those that were not anticipated?
Any help or links would be greatly appreciated!
Thanks,
Bob
[Non-text portions of this message have been removed]
Unlimited freedom, unlimited storage. Get it now, on http://help.yahoo.com/l/in/yahoo/mail/yahoomail/tools/tools-08.html/
[Non-text portions of this message have been removed]
.