RE: Debugging messages in Output window



What I'm looking for is that the only the items that appear in the Output
window are the ones I send using System.Console.Writeline (or Write) , i.e. I
do not want any messages such as those you listed in your 4th paragraph to
appear. Is this possible?
--
Ed


"Steven Cheng[MSFT]" wrote:

Hello Ed,

As for the "Redirect all Output window text to the Immediate window" option
of visual studio 2005, it is mainly used to redirect all the debugger
messages to the immediate windows, therefore not all the messages appear in
the output window will be redirected when we turn on this setting. For
example, those messages issue through the System.Diagnostics.Debug object
will be redirected(or some messages print through standard debugger API).

#General, Debugging, Options Dialog Box
http://msdn2.microsoft.com/en-us/library/85yzd16c(VS.80).aspx

However, those statements as below will still be displayed in the output
window:

'DebugThread.exe' (Managed): Loaded
'C:\WINDOWS\assembly\GAC_MSIL\System.Xml\2.0.0.0__b77a5c561934e089\System.Xm
l.dll', Skipped loading symbols. Module is optimized and the debugger
option 'Just My Code' is enabled.
The thread 0x17c4 has exited with code 0 (0x0).
The program '[17660] DebugThread.exe: Managed' has exited with code 0 (0x0).

Is there any particular requirement in your scenario that you redirect all
output window text to the immediate window? Please feel free to let me know
your detailed requirement and concern here and we may help you look for
some other possible ideas.

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead



==================================================

Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.



Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.

==================================================



This posting is provided "AS IS" with no warranties, and confers no rights.






.



Relevant Pages

  • Re: wpf: Trap keyup event in canvas
    ... you can do it in the window level. ... currentElement = e.OriginalSource; ... Microsoft Online Community Support ... where an initial response from the community or a Microsoft Support ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: DebuggerDisplay attribute Target property not working
    ... what was the idea behind changing the debugger display mechanism completely in VS2005 such that there is no backward compatibility with VS2003? ... I edit %user profile%\My Documents\Visual Studio ... Microsoft Online Community Support ... where an initial response from the community or a Microsoft Support ...
    (microsoft.public.vsnet.debugging)
  • Re: _asm { int 3 } doesnt work with VS2005 and VS6 on same machine
    ... XP to run the telephony services within the logged in user context or not ... use the asm int 3 technique at all anymore and just attach the debugger to ... Microsoft Online Community Support ... where an initial response from the community or a Microsoft Support ...
    (microsoft.public.dotnet.general)
  • Re: windows vista mouse cursor goes bezerk
    ... other than 0 or 1) for the timer is a generally good idea. ... If the timers are window based, check what window they are going to. ... be seen by our internal newsgroup support tool. ... where an initial response from the community or a Microsoft Support ...
    (microsoft.public.win32.programmer.ui)
  • RE: how to debug com interop in vs2005 under Vista
    ... as administrator" from the context menu. ... debugger and right click the VS2005 Exe to run it as Administrator. ... Microsoft Online Community Support ... where an initial response from the community or a Microsoft Support ...
    (microsoft.public.vsnet.debugging)

Loading