VS (2008) doesn't autoterminate cmd window

[lklawrie]

This likely isn't a IVF issue. But it's annoying.

VS2008, SP1
Debug mode.

If I forget to use the "Stop Debugging" menu item, I end up with a CMD window and no seeming way to terminate the process without a reboot.

I have even started another one without terminating one and then can terminate the 2nd but the 1st is still hanging around.

Any ideas for a better solution? (other than remembering to use "stop debugging" everytime)?

Linda

[Steven_L_Intel1]

Haven't run into that. How are you ending things other than "Stop Debugging"?

[IanH]

MS released a hotfix for Windows XP mid year for a problem with those symptoms - see this thread.

Before the fix came out a partial work-around was to remap Shift-F5 from "Stop debugging" to "Detach process", otherwise the task bar could get rather busy with all the dead console windows by the end of the day.

[lklawrie]

Quoting Steve Lionel (Intel)

Haven't run into that. How are you ending things other than "Stop Debugging"?

Usually, Steve, it's a "oh that's the problem", correct the code and then end VS -- but the cmd window gets left open. Or, having corrected the code, start a new run to see if that did it, without terminating the first.

Absent minded. Annoying. Not something terrible. If I used the debugger more, I would get used to always doing the "stop debugging", maybe. (I also couldn't find the task in the task manager window so I don't know if it can be stopped or not).

Linda

[Steven_L_Intel1]

I had forgotten about the Windows bug Ian mentioned - that's almost certainly the issue.