Workaround for over-debugging output "Event X is raised using Y arguments, but it is determined by Z parameters (s)"

Examples in the debug window in VS2017 (but also in other versions of VS):

Event 7 was called with 5 argument(s) , but it is defined with 6 paramenter(s).

Finding the reason: TPL ETW events have additional parameters that trigger an excessive debugger Filter your own message from the Visual Studio 2015 output window

But until an update or similar fix occurs - any suggestions for workarounds ? (code / tools / ???)

I really want my debug output window to work and not be laid out with the same (useless) message.

Disabling certain types of messages in the output window does not cost anything since it deletes the output messages that I want. ( Disable noise messages in debug output windows - visual studio 2012 )

We also tried to find a VS extension that could filter, but no luck.

Down this strip, VSColorOutput can probably be used to match RegExp, and then change the color of this message to the same color as the background in the output window ... but it seems really nasty, and will give endless empty lines in output window.

+4
source share

Source: https://habr.com/ru/post/1681257/


All Articles