Groups | Blog | Home
all groups > visual studio .net debugging > july 2006 >

visual studio .net debugging : Output-window: Debug-class is not writing.


Michael Maes
7/26/2006 5:00:02 AM
Hi,

With VS2005 (WinForm) the Output-Window ("suddenly") is not showing any
'Program Output' anymore (Module loading, Thread exits, ... are displayed
well).
So creating a new WinForm app and placing a simple
'Debug.WriteLine("HELLO")' in the Form-Load Event, doesn't write "HELLO" to
the Output-Window.
The option 'Program Output' on the Output-Window is checked.

We did have a change in our network lately (new domain) which might have
affected this behavior?

Anyone any clues?

Thanks!

Michael Maes
7/26/2006 10:27:01 PM
Hi Jeffrey,

Thanks for your reply.
I think the answer to all your questions is 'yes' :-)
Do you know a way to stop the redirect of the 'Program Output' (other output
remains in the Output-Window) to the 'Immediate-Window'?

TIA,

Michael

[quoted text, click to view]
jetan NO[at]SPAM online.microsoft.com (
7/27/2006 12:00:00 AM
Hi Michael,

Thanks for your feedback!

You may give the following setting a check:
VS2005 menu "Tools"->"Options..."->"Debugging" node->"General"->"Redirect
all Output window text to Immediate Window".

Uncheck it, if it is checked.

Hope this helps!

Best regards,
Jeffrey Tan
Microsoft Online Community Support
==================================================
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.
jetan NO[at]SPAM online.microsoft.com (
7/27/2006 12:00:00 AM
You are welcome :-)

Best regards,
Jeffrey Tan
Microsoft Online Community Support
==================================================
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.
Michael Maes
7/27/2006 1:38:01 AM
Many thanks Jeffrey!

[quoted text, click to view]
jetan NO[at]SPAM online.microsoft.com (
7/27/2006 2:34:23 AM
Hi Michael,

Thanks for your post!

This looks like a strange issue. If you stop the application and press F5
to debug the application, is there anything output generated in the Output
Window? Also, you'd better take a look at Immediate Window, I suspect if
the output is redirected to Immediate Window.

Additionally, if you create a new simple project, can this be reproduced?

Finally, I do not think network lateness will cause this problem, if you
have suspect over this, you may try to remove the network and do the test.
If the problem remains, it means that network is not the root cause.

Thanks.

Best regards,
Jeffrey Tan
Microsoft Online Community Support
==================================================
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.
AddThis Social Bookmark Button