yes several. CATCH should always log. Not logging trace allows you to wait for users to report the problems or hides them entirely; the users won't they wil just curse your app.
The Microsoft Application Block are what many would recommend but I have to ay go for Log4net instead it is much much much better. http://logging.apache.org/log4net/ allows logging to SQLserver, other DBs, XML files, custom loggings, supports levels of details in logging and much more. also go to: http://www.learnasp.com/ref and choose "Errors" and some stuuing articles will appear on the subject. On 5/14/05, P P <[EMAIL PROTECTED]> wrote: > Hi All > > I have a question with regards to using Try/Catch > block within my code, and this question arose after a > argument with my colleues:-) > > I personally believe it's safe and good practice to > use try/catch block within each Method/Function, per > them it is not really required (nobody amongst us had > real justification for why / why not required) > > Anybody has any other sugestions or comments? Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/AspNetAnyQuestionIsOk/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
