Search

VS 2012 Debug.Writeline output does not appear in the Output Window by Dan1

Active

1
0
Sign in
to vote
Type: Bug
ID: 778765
Opened: 2/7/2013 11:30:33 AM
Access Restriction: Public
0
Workaround(s)
0
User(s) can reproduce this bug
Environment

OS Windows Server 2008 R2 SP1.
VS 2012 Professional
Language VB
I compiled in Debug mode.
The "Show Output from" is on Debug.

The problem

The Output window Debug does contain "Load" lines but no Debug.Writeline.
The Immediate window contains the Debug.Writeline
Repair VS did not help.
Details (expand)

Visual Studio/Team Foundation Server/.NET Framework Tooling Version

Visual Studio 2012

Steps to reproduce

Develop a program including at least one Debug.Writeline
Run in Debug Mode
Look in the Output window with "Show output from Debug".

Product Language

English

Operating System

Windows Server 2008 R2 SP1

Operating System Language

English

Actual results

No Debug.writelines in the Output window

Expected results

Debug.writelines in the Output window
File Attachments
0 attachments
Sign in to post a comment.
Posted by Microsoft on 2/11/2013 at 11:03 PM
Thanks for your feedback. Based on your description, I will close this issue. If at any time your issue is closed unsatisfactorily, you may edit your issue via Connect and change the status to “Active.”
Posted by Dan1 on 2/7/2013 at 11:54 PM
Thanks, that was the cause.
Posted by Microsoft on 2/7/2013 at 9:45 PM
Hi Dan1,

Debug.WriteLine calls may not display in the output window if you have the Visual Studio option "Redirect all Output Window text to the Immediate Window" checked under the menu Tools > Options > Debugging > General. To display "Tools > Options > Debugging", check the box next to "Tools > Options > Show All Settings".

Would you please help to verify if you have that options checked?
Posted by Microsoft on 2/7/2013 at 11:50 AM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)
Sign in to post a workaround.