Could you provide an option to forward all output to the 'OutputDebugString' API ?

[janwilmans]

I'm the author of debugview++, a problem I experience is that if I debug a program with visual studio the application sends to the OutputDebugString API is redirected/caught by the visual studio output window.

I provide an vs extension to send everything that is written to the output window to the OutputDebugString API, however, its a very limited extension, I wondered if you could just add this functionality in VSColorOutput

[mike-ward]

Do you have the source for your extension?

[janwilmans]

Yes, it is here https://github.com/CobaltFusion/DebugViewPP/tree/master/OutputForwarderVSIX

…

On Sat, 18 Aug 2018 at 19:21, Mike Ward ***@***.***> wrote: Do you have the source for your extension? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#77 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AFqJhP30YfRGSucusfrXEDCqLzw-am3Zks5uSE0MgaJpZM4WCU_a> .

-- Jan

[janwilmans]

basically all it does is:
https://github.com/CobaltFusion/DebugViewPP/blob/master/OutputForwarderVSIX/Forwarder.cs#L71

take all the changes from GUID_BuildOutputWindowPane or GUID_OutWindowDebugPane
and write them to Trace.Write("")

It would be nice to be able to choose either or both:

[Settings]
Forward output to Trace.Write:
[x] Build Output (GUID_BuildOutputWindowPane )
[x] Debug Output (GUID_OutWindowDebugPane )

[mike-ward]

So if I understand, this is so you can see the output in other programs attached to the debugging session?

[janwilmans]

Exactly, the debug output windows of visual studio cannot be filtered, highlighted or anything really. Thats why I created Debugview++ (https://github.com/CobaltFusion/DebugViewPP) , it allows extensive filtering/highlighting and also different views. Greetings, Jan

…

On Tue, 28 Aug 2018 at 15:35, Mike Ward ***@***.***> wrote: So if I understand, this is so you can see the output in other programs attached to the debugging session? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#77 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AFqJhBtYqucO03vikbKQ-ZNFijn4UeQuks5uVUcUgaJpZM4WCU_a> .

-- Jan