Having the output of a Console App in Visual Studio instead of the Console?

In the Visual Studio Options Dialog -> Debugging -> Check the "Redirect All Output Window Text to the Immediate Window.

In the Visual Studio Options Dialog -> Debugging -> Check the "Redirect All Output Window Text to the Immediate Window".

Use System.Diagnostics. Trace Depending on what listeners you attach, trace output can go to the debug window, the console, a file, database, or all at once. The possibilities are literally endless, as implementing your own TraceListener is extremely simple.

Yes, but what I want to know is if it is possible to just do it, without having to implement it by myself. – devoured elysium Mar 30 '10 at 3:14 @devoured The Trace class outputs just to the debug window by default. You only need to attach extra listeners (and there are several already written you can use) if you want to also see the output elsewhere.

– Joel Coehoorn Mar 30 '10 at 3:29 I went to my Debug Options dialog and chose "Redirect all Output Window text to the Immediate Window" to make the Trace output go to the Immediate window so it doesn't get all mixed up with the debug crap. – Gabe Mar 30 '10 at 3:41.

You could create a wrapper application that you run instead of directly running your real app. The wrapper application can listen to stdout and redirect everything to Trace. Then change the run settings to launch your wrapper and pass in the path to the real app to run.

You could also have the wrapper auto-attach the debugger to the new process if a debugger is attached to the wrapper.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.