Debug.writeline where is the output

So, I am used to using Console. Writeline during development to generate debugging output and then remove them and comment them out when no longer needed. But the output is simply not appearing in the Output window Show output from: Debug where I was expecting it and where I see it in VS What might I have overlooked?

I created a new little app from the template just as a test - and it doesn't show up on that one, either. Attachments: Up to 10 attachments including images can be used with a maximum of 3.

Yes it was checked. I have only been using for a week or so, and had not changed much, and it is certainly possible that I checked that box in an attempt to make the Console.

WriteLine output visible. So, yeah, that helps, in that now Debug. WriteLine goes to the Output window which is useful, because the Output window persists even after one stops debugging the application.

But the question still remains: where is Console. WriteLine output going, and why isn't it showing up in the Output window, as it did in VS ? Was this an intentional change? Was it documented anywhere? Certainly seems to violate the "principle of least surprise". Hi JayJaeger ,. Typically, Console. Diagnostics class library the Debug class or the Trace class to send messages to the Output window. But under certain circumstances, Console. WriteLine also works and the message will appear in the Output window.

I tested on my side and I noticed that the Console. WriteLine did show the message in my Output window. If the answer is helpful, please click " Accept Answer " and upvote it. Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread. The params in C or ParamArray in Visual Basic keyword in the syntax for this method implies that the object array can be a single value.

The exception to this is the String object. Explicit overloads take precedence, so an arg value of a single string will default to the Debug. WriteLine String, String overload. This method calls the TraceListener. WriteLine method of the trace listener. Then, if the TraceLevel is set to Verbose , the example outputs the second error message on the same line as the first message.

An object whose name is sent to the Listeners. Then, if the TraceLevel is set to Verbose , the example outputs the name of the object on the same line as the first message. The second message is followed by a line terminator. Feedback will be sent to Microsoft: By pressing the submit button, your feedback will be used to improve Microsoft products and services. Privacy policy. Skip to main content. This browser is no longer supported. Download Microsoft Edge More info.

Create a free Team What is Teams? Collectives on Stack Overflow. Learn more. Where does System. Write output appear? Ask Question. Asked 12 years, 3 months ago. Active 1 year, 8 months ago. Viewed k times. Write "Hello via Console! Write "Hello via Debug! Write "Hello via Trace! I'm not using Visual Studio for any of my development, this is pure commandline stuff.

Improve this question. Peter Mortensen 29k 21 21 gold badges 97 97 silver badges bronze badges. Frerich Raabe Frerich Raabe Add a comment.

Active Oldest Votes. Improve this answer. It was useful didn't expect that for me to find out that Debug and Trace objects use the same trace listeners, therefore, both Debug. Write and Trace. Write will not work the same as a trace. WriteLine, the line executes, but nothing appears in the output window, anyone got any other advise? You need to add a TraceListener to see them appear on the Console.

Out ; Debug.