Did you know... If you do a Ctrl+F5 on a console application, the console stays open - #317

Did you know… If you do a Ctrl+F5 on a console application, the console stays open - #317 : EasyCoded

Fri, 19 Sep 2008 13:12:41 GMT

PingBack from http://www.easycoded.com/did-you-know-if-you-do-a-ctrlf5-on-a-console-application-the-console-stays-open-317/

re: Did you know... If you do a Ctrl+F5 on a console application, the console stays open - #317

Radu — Fri, 19 Sep 2008 14:17:09 GMT

It's annoying indeed that, when debugging a console application, the process terminates without a message (as when running without the debugger).

The solution is to set a breakpoint on the last instruction in the Main method. But not once I forgot to set it and had to re-start the debugger. In my opinion it will be worth to consider it as a fix in a future update for Visual Studio.

Thanks.

re: Did you know... If you do a Ctrl+F5 on a console application, the console stays open - #317

Jonathan Conley — Fri, 19 Sep 2008 19:31:35 GMT

I agree. I can find no logical reason for it to not stop while debugging and dose stop when not. However when has Microsoft done any thing Logical.

re: Did you know... If you do a Ctrl+F5 on a console application, the console stays open - #317

Ricardo Villamil — Fri, 19 Sep 2008 21:32:33 GMT

Radu, I don't think is annoying, I think is by design, otherwise how would VS know where and when to stop?

I somwhat agree with Sara, that if you run in the debugger there should still be the message Press any key to continue... but when you get this msg it means the application has already exited, so what good is it to have this message in the debugger if you can't pause or examine your code (remember, the app is already finished running when you get this message). The only thing you could do is...well...hit any key to exit and go back to VS.

The solution is, if you're going to use the debugger, you definitely need to have breakpoints or Debug.Stop() in your code. Leave that job to the developer, not to VS to guess where to stop/pause.

Thanks!

re: Did you know... If you do a Ctrl+F5 on a console application, the console stays open - #317

Mike Ward — Fri, 19 Sep 2008 22:10:01 GMT

I usually put the body of my main into a try/finally block. The finally block then does a check to see if it is running in the debugger and breaks if that's the case. Check out

http://blueonionsoftware.com/blog.aspx?p=1e4f3e2c-c631-40a7-9176-25a677c93b0c

on how to do this.

re: Did you know... If you do a Ctrl+F5 on a console application, the console stays open - #317

Eber Irigoyen — Fri, 19 Sep 2008 23:38:56 GMT

WOOT!!... I've always added Console.Read() to my little console apps, to do just that

nice... yeah, it seems backwards, but I don't care

re: Did you know... If you do a Ctrl+F5 on a console application, the console stays open - #317

Rogelio Rodriguez — Sat, 20 Sep 2008 02:42:21 GMT

console.ReadLine()

should stop the window from closing too.. just put it in your last line... before end module and end sub

re: Did you know... If you do a Ctrl+F5 on a console application, the console stays open - #317

The Danish Dynamo — Sun, 21 Sep 2008 21:13:50 GMT

In addition to the above suggestions, you can use the Debugger.IsAttached property to conditionally wait for user input, and there are other paths e.g. directives.

<pre>

if (System.Diagnostics.Debugger.IsAttached) {

Console.WriteLine("Press any key to continue . . .");

Console.ReadKey();

}

</pre>

Stop complaining about Microsoft products, they are better than the rest. The limitations are in your mind, the possibilities are endless.

re: Did you know... If you do a Ctrl+F5 on a console application, the console stays open - #317

X.Y. — Mon, 22 Sep 2008 12:38:38 GMT

"Stop complaining about Microsoft products, they are better than the rest. The limitations are in your mind, the possibilities are endless."

Very funny.