Stop debugging (Shift + F5), which will lead to a reboot

Question

I am using Visual Studio 2008 Professional Edition for development. I noticed that whenever I test web applications or websites with Ctrl + F5 and stop debugging (or close the browser), debugging starts again as if I pressed Ctrl + F5 again.

Initially, I thought it might be due to the ctrl sticky key, but I checked and confirmed that the sticky keys on my machine are not enabled.

I searched the Internet and noticed that many others also ran into the same problem. But Microsoft says the problem is with the sticky key ctrl. (See http://connect.microsoft.com/VisualStudio/feedback/details/534915/stop-debugging-shortcut-key-shift-f5-causes-debugging-to-restart-instead-of-just-stopping )

Does anyone have any other ideas as to why this might happen (in case I might have missed some kind of updated forum)

Many thanks.!:)

Answer 1

I really like your question, as this happens to me sometimes and I don’t know why, after many years, I don’t believe that it is connected with sticky keys.

There are only two ways to stop debugging in this situation:

• Alt + D E = I press Alt + D ; to open the Debug menu, then E for "Stop Debugging". This is an alternative hotkey combination that will work.
• - click the stop button on the debug toolbar.
• (optional) Sometimes, when I cannot press teh Alt + D , I cannot get focus on the toolbar, and I press ctrl 5 times. Somehow the sticky keys are stuck, although I did not turn them on.

Hope this helps.

Answer 2

I also sometimes happen to me, and I also turned off StickyKeys. Sometimes I see this when I lock my computer. When this happens and I try to enter a password, the computer acts as if I press a control button.

My only suggestion is to use the menu to stop debugging, and then gently touch the control key twice, then try again. He always stops when I do this.

At heart, I wonder if this is due to conflicts of third-party utilities that intercept key combos for their triggers. SnagIt, Freesnap, AutoHotKey are the three that I use, but when the problem is so intermittent, you can't really turn them off and say, "yup, my problem is gone."

Answer 3

It may seem simple and may not be the answer for you, but it was for me. Somehow in Visual Studio 2015, my Shift + F5 got mapped to "Debug.Restart" and "Debug.StopDebugging" got reassigned to Ctrl + Alt + Break. Not sure if Resharper somehow messed up the shortcuts.

I was able to fix this by going to Tools ... Options ... Environment ... Keyboard, search for "Debug.StopDebugging" and assign it Shift + F5.

Answer 4

I also had the same problem. I also use Visual Studio 2008. Just click Tools → option → environment → Keyboard. And then install

to "Default".