Want to see text output when running console apps



Martinj gave me his pet peeve about wanted to see the text output when a console app
is run.  In Whidbey we’ll be fixing this problem by piping the output to an output
type window in the shell.  This way when the app exits your text will still be
there.  I hope this is an acceptable solution. It works for me. 🙂

Comments (3)

  1. Daniel O'Connell says:

    Sounds good, infact very good, as long as it still dumps out to the console as well, or the output like window in the IDE accepts input.
    I don’t think I’d want to deal with my interactive console programs via the console and the output window.

  2. MartinJ says:

    Yeah. That does work for console output. I guess the bigger issue to me is when running an app in the debugger versus outside it, the expected behavior should be the same.

    It’s almost the same as not really knowing how your app will look by just observing things in the designers. You have to run a project to see how it will really look. Imagine if you looked at a form in the designer, run it in the debugger, decide it’s good and publish it. When you finally see it live, it’s behavior is different than what you had been testing with all along.

    -Martin

  3. Josh Ledgard says:

    To be clear: If you have a console app that does not create a pause at the end itself (IE Runs, spits output, and terminates) it will not pause if you ran it from the Run prompt off of the start menu. The same thing happens if you run in the debugger. This is expected. The pause you see happens when you press (default keys) CTRL – F5. This pause is becuase we create a seperate wrapper called VCSpawn around the EXE. The wrapper, in this case, causes the pausing. It also has the accidental side effect of giving the user a pause at the end.
    josh

Skip to main content