----- Original Message ----- From: "Chris Jenkin" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, April 30, 2002 5:10 AM Subject: Re: [DOTNET] Trace question.
> Good ideas. I was hoping to avoid remoting...oh well. Can you expand on > OutputDebugString a little, not familiar with this. > > Thanks again, > > CJ > > -----Original Message----- > From: Ingo Rammer [mailto:[EMAIL PROTECTED]] > Sent: Monday, April 29, 2002 4:28 PM > To: [EMAIL PROTECTED] > Subject: Re: [DOTNET] Trace question. > > > > Also, while it would be windows specific, you might consider > > just looking for a a listening app that uses DebugActiveProcess > > and WaitForDebugEvent with a DEBUG_EVENT value of > > OUTPUT_DEBUG_STRING_EVENT because the > > System.Diagnostics.DefaultTraceListener implementation on > > windows broadcasts via OutputDebugString. I'm sure someone has > > to have already written one of these. > > Ahhh ... I didn't know this (.NET's use of OutputDebugString). You're > absolutely right here ... it should be way easier this way. > > Thanks, > -Ingo > > Author of "Advanced .NET Remoting" > http://www.dotnetremoting.cc > > You can read messages from the DOTNET archive, unsubscribe from DOTNET, or > subscribe to other DevelopMentor lists at http://discuss.develop.com. > > You can read messages from the DOTNET archive, unsubscribe from DOTNET, or > subscribe to other DevelopMentor lists at http://discuss.develop.com. > You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
