Got it. Thanks! Sounds cool!
On Wed, Mar 5, 2014 at 11:12 AM, Justin Dearing <zippy1...@gmail.com> wrote: > George, > > This does not display messages. This sends messages to Sysinternals > Process monitor (ProcMon.exe), a tool that display network, file and > registry activity. > > The advantage of sending the messages here instead of the kernel > DebugOutput mechanism (where DbgView or other can pick them up) is the > messages would be displayed inline with file, network and registry access. > > ProcMon receives and displays the messages.Wintellect's unmnaged dll send > messages to procmon. I don't need to actually use wintellects DLL. I can do > it entirely with PInvoke though. > > Justin > > > > On Wed, Mar 5, 2014 at 1:52 PM, George Chung <geo...@glympse.com> wrote: > >> Hi, >> Just curious. How does Wintellect's app differ from Dbgview (which also >> displays Trace/OutputDebugWindow messages)? >> >> Cheers >> >> >> On Tue, Mar 4, 2014 at 5:41 AM, Justin Dearing <zippy1...@gmail.com>wrote: >> >>> Hello, >>> >>> Wintellect released some code that allows you to send trace messages to >>> procmon. I wrote an appender that let's you tap into that with log4net. I'm >>> getting it reviewed and will send wintellect a pull request. >>> >>> https://github.com/zippy1981/ProcMonDebugOutput/tree/log4net >>> >>> If I were to make an appender without the dependency on Wintellect's C++ >>> code, could that be added to the log4net built in Appenders? >>> >>> Regards, >>> >>> Justin Dearing >>> >> >> >
