John Saunders wrote:
> "José Joye" <jose.joye@KILLTHESPAMSbluewin.ch> wrote in message
> news:%23LSc0dxjDHA.2528@TK2MSFTNGP12.phx.gbl...
>> Maybe the tools from SysInternals is what you are looking for. It
>> will catch all call make to Trace.WriteLine:
>>
>> http://www.sysinternals.com/ntw2k/fr...ebugview.shtml
>
> I took a look at the above URL, but it doesn't say anything about
> capturing the output of Trace.WriteLine.

Jose means the output from the standard DefaultTraceListener class which
generates messages using OutputDebugString. DebugView is an excellent tool
to do this. BTW OutputDebugString is a double edges sword because it couples
your application to the application reading the strings. If the reader
program is not written correctly (eg you put a large delay in the code that
reads the debug strings) then the thread writing the strings will be
blocked. DebugView is well written, of course :-). The VS.NET debugger will
also read OutputDebugStrings, but only for the process that is being
debugged. DebugView will do that for _all_ processes.

Richard
--
my email evpuneqt@zicf.bet is encrypted with ROT13 (www.rot13.org)