Visual Studio obstructing DebugView

re: Visual Studio obstructing DebugView

Jake Scott — Mon, 20 Nov 2006 00:20:43 GMT

Just setup a filter in Debug View. In the exclude textbox type "Enter HWND" without the double quotes. Problem solved.

re: Visual Studio obstructing DebugView

SvenC — Mon, 28 Aug 2006 12:00:04 GMT

I tracked that down: it's actually caused by the latest Visual Source Safe addin: ssscc.dll

I searched that dll for the offending text "Left, Enter HWND" and replaced the first character of that text in the dll with a null byte. So OutputDebugString will just output an empty string which is not appearing in my DebugView.

Now I have silence in debugview again until my OutputDebugStrings are executed.

HTH,

SvenC

re: Visual Studio obstructing DebugView

Dan McKinley — Tue, 20 Jun 2006 18:52:33 GMT

I was wondering when somebody else would notice this. It's been driving me nuts for a while.

http://mcfunley.com/cs/blogs/dan/archive/2006/03/30/978.aspx

re: Visual Studio obstructing DebugView

AvnerK — Tue, 20 Jun 2006 16:12:59 GMT

I can always filter, but since the 3448 is the Process ID for the current instance, it changes every time I run Visual Studio. This means I can either redefine the filter every time or try to guess all the possible messages and filter them out.

re: Visual Studio obstructing DebugView

Chris — Tue, 20 Jun 2006 15:25:08 GMT

That's what filters are for. Just set it to exclude 3448 or whatever all the VS debug lines start with.

My UPS software does the same thing, so i either have to set up filters, or unplug the USB interface and lose my auto hibernate and auto shutdown ability that the UPS can trigger.

Interesting Finds: June 20, 2006 AM edition

Jason Haley — Tue, 20 Jun 2006 14:40:40 GMT

re: Visual Studio obstructing DebugView

merrion — Tue, 20 Jun 2006 09:41:27 GMT

If there are no Trace listeners attached the default is to send any Trace.WriteLine type output using OutputDebugString - see http://www.thecodeproject.com/vb/net/VisualTraceListener.asp