When I run my .net 4.0 winforms application, I see tons of output in debugview (the following is an excerpt). I routinely use debugview for debug messages so all this extra stuff can get quite noisy.
[8092] *** HR propagated: -2147024774
[8092] *** Source File: d:\iso_whid\x86fre\base\isolation\com\enumidentityattribute.cpp, line 144
[8092]
[8092]
[8092] *** HR originated: -2147024774
[8092] *** Source File: d:\iso_whid\x86fre\base\isolation\com\copyout.cpp, line 1302
[8092]
[8092]
[8092] *** HR propagated: -2147024774
[8092] *** Source File: d:\iso_whid\x86fre\base\isolation\com\enumidentityattribute.cpp, line 144
[8092]
[8092]
[8092] *** HR originated: -2147024774
[8092] *** Source File: d:\iso_whid\x86fre\base\isolation\com\copyout.cpp, line 1302
Does anyone know why this happens, and if/how I can prevent it?
I searched forever online before posting this question, but of course I find something as soon as I ask it.
This is a bug already reported here: http://connect.microsoft.com/VisualStudio/feedback/details/535084/vs2010-debug-output-should-be-cleaned-up
Apparently, there are many aspects to this verbose debug output so it will take some time (next .net release) to get all the fixes released.
VS 2010 SP1 is available now.
Workaround is to add some Exclude filters, but doesn't exclude blank lines:
*originated*;*iso_whid*;*propagated*; ;
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With