Logging Checklist

 < Day Day Up > 



Just about any application should ship with a way to collect runtime logs. When equipping your application for logging, consider these points:

  • Use logging during development to collect information that you can’t get by running the code in the debugger.

  • Use logging after shipping to collect the same information that you’d look for in the debugger.

  • Provide an easy way to turn logging on and off at runtime, to avoid the overhead of continuous logging.

  • Use the Trace class or the log4net package to implement logging for stand-alone applications.

  • Use the Enterprise Instrumentation Framework and the Logging Application Block to implement logging for distributed applications.

  • Be prepared to replace or supplement logged information with diagnostic information.

One good use for logs is to share information among the members of a team, particularly when the entire team is not located in the same place. In the next chapter, I’ll look at some of the other issues involved with small development teams.



 < Day Day Up > 



Coder to Developer. Tools and Strategies for Delivering Your Software
Coder to Developer: Tools and Strategies for Delivering Your Software
ISBN: 078214327X
EAN: 2147483647
Year: 2003
Pages: 118

Similar book on Amazon

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net