http://blogs.msdn.com/b/darrenj/archive/2007/04/03/watch-out-debugview-outputdebugstring-performance.aspxFor developer level tracing the tracing classes held within the System.Diagnostics namespace are often used along with the Windows Sysinternals DebugView tool. Tracing events are written to OutputDebugString via the DefaultTraceListener trace listeneren-GBTelligent Evolution Platform Developer Build (Build: 5.6.50428.7875)http://blogs.msdn.com/b/darrenj/archive/2007/04/03/watch-out-debugview-outputdebugstring-performance.aspx#2301901Fri, 27 Apr 2007 21:40:52 GMT91d46819-8472-40ad-a661-2c78acb4018c:2301901Terry Carvin<P>We are using this heavily at the moment and in fact we are guilty of using it on production. However we are integrating the use of the Enterprise framework so that we have fine grained control the amount and type and application area we wish to output. I have combined this with a custom trace listener that improves on the standard database listener to log output to a single SQL server table. I'm thinking we may be able to integrate ETW here, or is it worth waiting for Enterprise Framework 3.0. I haven't seen anything about ETW in 3.0, maybe i could create an ETW implementation. Is it worth the effort or is this premature optimisation.</P><div style="clear:both;"></div><img src="http://blogs.msdn.com/aggbug.aspx?PostID=2301901" width="1" height="1">