Forgot to add that this would only run when the user turns on debugging.
Message from Bob Provencher <[EMAIL PROTECTED]>@DISCUSS.DEVELOP.COM received on 08/25/2005 09:24 AM 08/25/2005 09:24 AM Bob Provencher <[EMAIL PROTECTED]>@DISCUSS.DEVELOP.COM Please respond to "Unmoderated discussion of advanced .NET topics." <[email protected]> Sent by "Unmoderated discussion of advanced .NET topics." <[email protected]> To: [email protected] cc: Subject: Re: [ADVANCED-DOTNET] Writing code for Debugging >> 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). << >> 1) What have you done in the past to help debugging? Code instrumentation is key and should be part of your architectural design very early IMHO. I've done a variety of things but I like to use the capability of listeners to route debug output various places. There is an MS pattern for instrumentation and logging you should look at. >> 2) Is there a better way then my idea above? I don't think you want to log each and every function call that way. 99.9% of the time everything will work fine and you will be logging a ton of stuff for nothing taking a large performance hit. Log as much as you think you will need when an exception occurs, not all the time, and make sure your app is checking for, catching, logging and handling exceptions appropriately and correctly. =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
