While we appreciate comments from our users, please follow our posting guidelines. Have you tried the Cyotek Forums for support from Cyotek and the community?
Styling with Markdown is supported
27 April 2019 Reply
This is quite messed up for console apps. The checkbox does nothing for a run under the debugger. It closes the output window whatever the checkbox is set to. This is the old behavior for debug runs. HOWEVER, for non-debug running of debug compilations, the new default if that the box is unchecked and the window closes immediately. Setting the checkbox (automatically close the console when debugging stops) changes the non-debug run to leave the console window open at the end of execution. Totally confusing and mislabeled. WORSE: if you are running Visual Studio 2017 also, the options apply there also, so you suddenly lose the output window in non-debug runs.
28 April 2019 Reply
Thanks for taking the time to comment. I have to say, I didn't observe this behaviour myself. I never tried running non-debug builds as it is incredibly rare I build in release mode and then run it via Visual Studio, but my observations were it worked perfectly in debug mode for .NET Core console applications - I already noted that sadly it doesn't work for full .NET Framework applications, even in the RTM version (which is a shame, I still currently do more work in the full framework than core).
I don't have an answer on your woes with the output window either, while I'm currently running VS2019 on a fresh Windows install, prior to the RTM I was running both 2015 and 2017 and never identified any problems - the shells are seperate products with seperate configurations etc. That doesn't mean that VS2019 has some subtle bug of course, just that it's nothing I've experienced myself.