RE: Debugging messages in Output window
- From: Ed White <ewhite@xxxxxxxxxxxxxxxxx>
- Date: Fri, 9 Feb 2007 07:40:01 -0800
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.
- Follow-Ups:
- RE: Debugging messages in Output window
- From: Steven Cheng[MSFT]
- RE: Debugging messages in Output window
- References:
- RE: Debugging messages in Output window
- From: Steven Cheng[MSFT]
- RE: Debugging messages in Output window
- Prev by Date: RE: VS 2005 won't hit breakpoints when debugging an executable
- Next by Date: Re: Remote Debugging
- Previous by thread: RE: Debugging messages in Output window
- Next by thread: RE: Debugging messages in Output window
- Index(es):
Relevant Pages
|
Loading