I’d like to create a small console application that on-demand, for troubleshooting purposes, I can start to display traces from another local client application. I’ve been considering numerous approaches some somewhat older such as posting WM_USER messages (oldish and there is probably a max size limit for messages), OutputDebugString (or .NET Trace class methods) + some filtering to recognize messages coming from the specific application, named pipes (do not allow fire-and-forget tracing as a connection needs to be awaited between client and server), other IPC methods such as WCF (not lightweight as I’d like). I was looking at anonymous pipes that don’t seem to require client and server to wait for each other for the tracing to be done. I don’t need real logging but simply traces that can be captured and be displayed if needed.