Ctrl key stuck after doing illegal action while debugging - by ee9

Status : 

  Deferred<br /><br />
		The product team has reviewed this issue and has deferred it for consideration at a later time.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 776361 Comments
Status Closed Workarounds
Type Bug Repros 0
Opened 1/11/2013 11:25:12 AM
Access Restriction Public


This happens when I Ctrl-X code and an error:

Microsoft Visual Studio
Editing or deleting an active statement which is not at the top of the callstack will prevent the debug session from continuing while Edit and Continue is enabled.

appears. It sometimes (not always) makes Visual Studio think Ctrl is still being held, and key combos like Shift-F5 are recognized as Ctrl-Shift-F5 which leads to unexpected actions.

This also happens when commenting code with Ctrl-K, Ctrl-C which leads to the above error popup.
Sign in to post a comment.
Posted by VISHMAYSHAH on 7/13/2015 at 2:37 AM
i have reproduce this issue in VS2010,
Steps are
1. Start Debugging
2. Click ctrl+x to cut a line in locked pages
3. It will not let you change
4. Now, Click x,s,tab,Shift+F5 and you will find the error
Posted by Microsoft on 3/5/2013 at 10:44 AM
Thanks for your feedback. Unfortunately, at this stage in the product cycle we are unable to address this for the current release as we are only taking critical and high priority bug fixes. We have logged your suggestion and will take it into consideration for next version planning. Even though we cannot always act on every issue reported, we do like to hear feedback, so please don’t hesitate to file an issue.
Malcolm Dickson
IDE Experience Program Manager
Posted by ee9 on 2/21/2013 at 4:41 AM
This only affects VS, other applications don't think the key is being held down.
Posted by Macy [MSFT] on 2/20/2013 at 8:15 PM

Does this happen just on VS or system-wide(ie impacts notepad or other applications)?

Microsoft Visual Studio Connect Support Team
Posted by ee9 on 2/7/2013 at 10:26 PM
Why was this marked as resolved, when there is no solution posted or linked to?
Posted by Macy [MSFT] on 1/13/2013 at 10:17 PM
Thanks for your feedback.

We are rerouting this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.
Posted by Macy [MSFT] on 1/11/2013 at 11:51 AM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)