You'll want to take a close look at the System.Diagnostics.Trace class. It's configurable (via app.config) to allow optional, and conditional output via Trace.WriteLineIf() and Trace.WriteIf()--which allow you to do things like output just errors, errors and/or warnings, errors and/or informational and/or warnings.
Exceptional C# (Bill Wagner) has a good section on the above (Item 36). You should also have a look at the Exception Handling Application Block (http://msdn.microsoft.com/library/default.asp?url=/library/en- us/dnpag2/html/ehab.asp ) http://www.peterRitchie.com On Thu, 25 Aug 2005 09:13:52 -0500, Franklin Gray <[EMAIL PROTECTED]> wrote: >I've been given the task of coming up with a standard for our new app for >help in debugging the code when a client calls in and has a problem. So >far, all I can think of is to log all variable values at the beggening of >all functions and logging the output of all functions. Also logging all >screen data (if grid, only current row). > >Questions: > >1) What have you done in the past to help debugging? > >2) Is there a better way then my idea above? > =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
