Home Dashboard Directory Help
Search

Ctrl Key stuck during debugging? by Justin Minnaar


Status: 

Closed
 as Not Reproducible Help for as Not Reproducible


2
0
Sign in
to vote
Type: Bug
ID: 685741
Opened: 8/25/2011 11:58:23 PM
Access Restriction: Public
Moderator Decision: Sent to Engineering Team for consideration
0
Workaround(s)
view
2
User(s) can reproduce this bug

Description

While debugging, CTRL is active, so pressing Shift+F5 causing program to restart debugging, as if Ctrl+Shift+F5 was pressed.

Whilst this is a simple issue, it has been annoying me for years so I felt it was worth reporting. Perhaps you can just do a clear of the CTRL key status when Visual Studio receives focus?
Details
Sign in to post a comment.
Posted by sagoo33 on 4/12/2012 at 5:33 PM
This is easy to reproduce:
Run a C# project in debug mode, select a code window, attempt to paste something using Ctrl+V, Popup is shown, click ok, then hit Shift+F5 to stop attempt to stop debugging, VS 2010 SP1 still thinks Ctrl is being held down, so the debugging is restarted. This is rather annoying...
Posted by MS-Moderator10 [Feedback Moderator] on 9/2/2011 at 12:19 AM
Thank you for submitting feedback on Visual Studio 2010 and the .NET Framework. At this point, it has been more than 7 days since we initially requested additional information to reproduce your issue. Since we have not heard back from you we will close the issue. If you need further assistance on this or any other pre-release product issues in the future, please feel free to contact us and we will be happy to help.
Posted by MS-Moderator10 on 8/29/2011 at 12:43 AM
I am currently standing by for an update from you and would like to know how things are going on your end. If you could get back to me at your earliest convenience with information I request, we will be able to make headway towards a resolution. I look forward to hearing from you.
Posted by MS-Moderator10 on 8/26/2011 at 2:23 AM
Thanks for reporting the issue.

In order to fix the issue, we must first reproduce the issue in our labs. We are unable to reproduce the issue with the steps you provided.

Please export and reset environment settings file by clicking Tools-> Import and Export Settings, after that, please send it to us so that we can conduct further.

Please try this (from a Visual Studio command prompt with devenv in the path):

devenv /resetuserdata

Thanks again for your efforts and we look forward to hearing from you.

Microsoft Visual Studio Connect Support Team
Posted by MS-Moderator01 on 8/26/2011 at 12:42 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)
Sign in to post a workaround.