Visual Studio 2010: Editor stops responding to keyboard

Question

I\'ve got this very odd bug that appears to be a quirk in Visual Studio 2010: Sometimes, when moving the cursor into double quotes of a CSS style=\"\"

Answer 1

I have encountered this using Visual Studio 2013 and Resharper 8.2.1. None of the solutions provided in this thread worked (even suspending and resuming Resharper)

After contacting JetBrains support, it turned out to be a caching issue.

Deleting all the files from the following directory solved the issue, as Resharper re-creates new caches:

C:\Users\[Username]\AppData\Local\JetBrains\ReSharper\v8.2\SolutionCaches\[Project_reference]

Answer 2

Using a source control (GIT, AKSVN)? If so, disable it, restart VS then enable it and open the solution again.

Answer 3

Just encountered the issue in VS 2012, in editing C#.
I noticed that the problem had occurred soon after the trial period of Resharper has ended and i inserted a valid license number. It also happened in only some of the source files.
The solution: Tools->Options->Resharper: Suspend.
Try typing - should work now.
Then: Tools->Options->Resharper: Resume.
Problem gone.

Answer 4

Empty the solution cache folder

C:\Users\{UserName}\AppData\Local\JetBrains\ReSharper\v8.2\SolutionCaches\

This was suggested by JetBrains support when I contacted them.

Answer 5

Permanently fixing... Not too sure however I found that pressing pressing Ctrl+Shift+Caps Lock+Tab all at once seems to get rid of this and enables the mouse and keyboard again. I know this isn't the best of solutions but it works.

Answer 6

I tried every other workaround here but nothing seemed to work, and the issue was only present in one solution but not another.

Disabling Resharper fixed it temporarily but it came back after re-enabling it which wasn't a viable long-term solution.

What worked for me was disabling all Resharper Extensions (Under Resharper -> Extension Manager). I was able to type again even after re-enabling all of them, so I'm unsure which extension specifically caused the issue, but that's another route to try for people who still have this issue.