logging
A recent Stack Overflow post described one programmer's logging style. Here's what he logs: INFO Level * The start and end of the method * The start and end of any major loops * The start of any major case/switch statements DEBUG Level * Any parameters passed into the
c#
I made a few improvements to the Logging TraceListener: * Files can now be aged by date as well as size * Filename is now completely templated using a single FileNameTemplate property, which supports standard String.Format codes for file number and date * Added separate properties to specify units of scale for
logging
I’m working on a console app that needs to provide integrated logging of its own output. Sure, you could do a standard console output redirect, but I wanted the app to be responsible for logging its own output. I decided to write my own TraceListener that automatically creates IIS-style
regular expressions
We’re currently supporting a third party application that, in addition to producing some truly impressive WTFs, generates incredibly verbose log files with zillions of ‘error messages’ that aren’t really errors. This makes diagnosing problems in their server code* very difficult. It is, however, a great use for a