Take the 2-minute tour ×
Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

Sometimes the Ctrl key gets stuck somehow during debug sessions in Visual Studio 2010, and when I press Shift+F5 to stop debugging, it gets reset (Ctrl+Shift+F5).

This gets very frustrating sometimes, especially when the solution builds a significant amount of time. How do I prevent this from happening ever again?


I just figured out this happens when I do Ctrl+Something and the error message appears right after that telling me I can't do that (not pressing the keys, but the result of the combo, like cutting some code or commenting).


Posted a bug report.


As you can see from the bug report page linked to right above, this issue is not likely to be fixed.

share|improve this question

3 Answers 3

up vote 4 down vote accepted
+50

This bug was reported in Microsoft Connect on September 2010 and reported as "solved in the next major release of Visual Studio".

Nevertheless, the bug was reported again on August 2011, and this time Microsoft was "unable to reproduce the issue".

To my way of thinking, there are two actions that you can take already:

  1. Report the bug again on Microsoft Connect with exact instructions on how to reproduce.
  2. As a workaround, remove or replace in the meantime the Crtl-Shift-F5 keyboard mapping.
share|improve this answer
    
I posted a bug report, let's see what happens. –  user1306322 Jan 11 '13 at 19:28

This is an old question, but maybe this answer will help someone else.

Problem: Control key appears "stuck" in VS. Works fine in other apps. Pressing Ctrl key does not toggle back to non-Ctrl mode. For example, arrow up scrolls page instead of moving cursor.

To reproduce: Ctrl-V to paste into read-only source while in debug mode.

To fix: Press right Ctrl key. Somehow that seems to un-stick it when the left Ctrl key won't.

share|improve this answer
    
It's not old. It's exactly one month since it was posted and I'm checking every day. Also you can fix this by pressing Ctrl+Shift which changes the language (where available). –  user1306322 Jan 21 '13 at 17:25

Because Visual Studio tracks the control key state using keyboard events, rather than checking it when responding to an event.

Therefore if the KeyUp event for the control key is sent to some other window, and that window swallows the event (marks as Handled), VS2010 will not receive the event notification, then the application will behave as though the ctrl key is still down until you press and release ctrl again (which will cause a keyup event).

This is pure conjecture based on the behavior I've seen (and your observations as well), so I don't know why I am bothering to post this...

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.