What Causes Visual Studio Keyboard Shortcuts to Change? (VS2019) - visual-studio

For example, 'find all references' was Ctrl + Shift + F12, now seems to be Ctr + K + R
Is this a user setting or changed during a new build of VS?

Shortcut is still same. I think you might have installed extensions like ReSharper, so it might be due to that. Please uninstall extension and then check.
Reference: https://developercommunity.visualstudio.com/comments/530592/view.html

The change could have many reasons: Change of keyboard language, the configuration file might have changed something or an extension was installed.

Related

CTRL+D is not working in vs code copy similar code

Previous in I have used ctr+d for duplicating the code many times, but when I switched to desktop and installed vs code and all the necessary extensions for my react project. And now this CTRL+D keyboard shortcut is not working. Can any help me to solve this issue
I recently met this issue too. I found a solution, see this: https://linuxpip.org/duplicate-lines-vscode/.
The main step are:
File > Preferences > Keyboard Shortcuts.
type "copy line",then you will see the related shortcuts.
remember the new shortcut(e.g. Shift + Alt + Down) or modify the shortcut to ctrl + D.
shift + alt + arrow-down works for me.
For me it was a VS Code extension causing the ctrl + ... binds not to work. It was "Vim emulation". Try isolating the issue by uninstalling the extensions until you find which one.
Similar issue for Windows 10, resolved using CTRL + F2.

alt+ctrl+f4 not working on visual studio 2005? but it did work previously

In VisualStudio .net (say 2005)
I have this shortcut Alt+Ctrl+F4 which closes all the opened windows. (Already mapped to window.closealldocuments)
and another one Alt+Ctrl+Shift+F4 to close all but this window.
Now both shortcuts used to work on my previous workstation.
Both having winxp 32.And i work on sv 2005 on both.
But on this new machine, Alt+Ctrl+F4 does not seem to propagate to Visual studio, like there's some other application or the explorer mapping this key to something else, and it's not propagating the event to vs process.
I know about the 'tools -> options...keyboard' in VS, but when I press the combination in the 'press shortcut keys:' field..
it would receive these combinations: Alt+Ctrl+F5->F10 but won't receive these: Alt+Ctrl+F1->F4.
It's like you didn't press nothing.
So now... any ideas?
the problem was a process that probably was receiving the key combination and not propagating it to the rest of applications.
in my case it was hkcmd.exe (intel's graphic something ) that captures key combinations to do certain things like display rotation and such.
anyway thanks hans passant for your comment.
These mappings aren't hard coded. Not sure what happened, but it is easy to remap them. Just go to Tools -> Options then:
Click in the top indicated text box, then press the key combination, and select the appropriate command for it. I like to use Ctrl + W to close the document and Ctrl + Shift + W for all.
You can set any hotkeys manually in any version of visual studio, just go to Tools->Options...-> Keyboard and assign any command to keys sequence

Navigate To (CTRL + comma) in Visual Studio does not work

The "Navigate To" function (CTRL + comma) does not work on my solution. It gets stuck on "Found 0 matching results" while the little progress bar stays there but is empty.
I searched for some kind of IntelliSense cache file next to the .sln, but all I found was a .suo file which I deleted but it did not help.
Why is it not working?
I had the same problem. I went to Tools > Options... > Environment > Keyboard and clicked Reset. Yes, it will reset any customizations you had, but I figured that was the problem for me (I had an add-in take over Ctrl-, and even when I disabled the add-in it wasn't working). Resetting the keyboard shortcut customizations did the trick.
The command is not "Navigate-To" but actually Edit-GotoAll and it has the keyboard shortcuts of Ctrl-T and the more known one of Ctrl-, (comma).
Reference Default keyboard shortcuts in Visual Studio
💡 Solution 💡
Here are the steps to resolve
Verify it is working by trying the opposite keyboard shortcut. If both shortcuts do not work type in "Edit Goto All" in the command search/execute box of Visual Studio.
Does the command work? If it does not work then do a reset via Visual Studio Options:
Then verify or add the keyboard command to the command in the mapping after the reset.
Type in "Edit.Goto" in the Window commands containing
Then selected Edit.Goto.All:
If you do not see the mapping (#3)
Add the keystroke in the box where bubble 4 is above and click Assign.
Set OK as shown on bubble step 5.
This is for Chinese user only. This is because of the Sogou Pinyin (搜狗输入法)occupy this shortcut system wide. And it won't release if you just uninstall it.
Go to here to disable it: Language->Advanced settings->Change language bar hot keys
Uninstall it is not working, you need disable that setting then uninstall it.
The Navigate To Feature does not use an on disk cache so that shouldn't be the issue.
The only thing I can think of that would cause this behavior is a bad Visual Studio install. I hate making this suggestion but have you tried repairing the install?
Tools > Options... > Environment > Keyboard and clicked Reset.That will work.If you installed the latest version/framework or re-sharper of visual studio then it may happens...
I just got the same problem and solve it by following the instruction I found here: http://social.msdn.microsoft.com/Forums/en-US/vssetup/thread/2bbab30e-3188-406b-b492-eabf8c2fbc0b/
For Chinese users, if you are using Sogou Pinyin, you can turn off Ctrl + Comma thru this.
Use spyxx_amd64.exe in this answer should work for most cases. https://stackoverflow.com/a/43645062/1179950
However, this didn't work for me... For my case, which is caused by language keyboard hotkey setting in Windows. By Sougou Pinyin though I have uninstalled it..
You can unset this in Control Panal (Windows 10):
Region&Language -> Advanced keyboard settings -> Language bar options ->Advanced Key settings panel
Unset all hotkeys you wont use!
For traditional Chinese users, you muse use the old version of new Cangjie.
Ctrl+Comma

Visual Studio keyboard shortcut to display IntelliSense

What's the keyboard shortcut for Visual Studio to display the IntelliSense box if one accidentally hits ESC and wants the box come back again?
Additionally, Ctrl + K, Ctrl + I shows you Quick info (handy inside parameters)
Ctrl+Shift+Space shows you parameter information.
Ctrl + Space
or
Ctrl + J
You can also go to menu Tools → Options → Environment → Keyboard and check what is assigned to these shortcuts. The command name should be Edit.CompleteWord.
The most efficient one is Ctrl + ..
It helps to automate insertions of using directives. It works if the focus is on a new identifier, e.g. class name.
Ctrl+Space should do it.
It should be Ctrl + J.
If you have arrived at this question because IntelliSense has stopped working properly and you are hoping to force it to show you what you need, then most likely none of these solutions are going to work.
Closing and restarting Visual Studio should fix the problem.
If you want to change whether it highlights the best fitting possibility, use:
Ctrl + Alt + Space
Alt + Right Arrow and Alt + Numpad 6 (if Num Lock is disabled) are also possibilities.
In Visual Studio 2015 this shortcut opens a preview of the definition which even works through typedefs and #defines.
Ctrl + , (comma)
On Visual Studio Community 7.5.3 on Mac this works for me:
Ctrl + Space
The shortcut to bring up the IntelliSense box is called Edit.ListMembers. It defaults to:
Ctrl + J
The shortcut to automatically select the most likely option is Edit.CompleteWord. It defaults to:
Ctrl + Space

How do I fix this Visual Studio keyboard mapping problem?

Something (who knows, possibly even me, though certainly not intentionally) has changed the keyboard mapping in Visual Studio 2008, and I cannot figure out how to get it back to the default.
The symptom that I see as the problem is that when I type the name of a class which is not in a namespace listed in the using statements at the top of the file, the shortcut to add that namespace to the file (expand tooltip), which is, by default, Ctrl + . (period) has been changed to Shift + Alt + F10. There are probably other key settings changed, but this is one that is really annoying me at the moment.
Ways I have already tried to fix the problem which have not worked
Tools, Options, Environment, Keyboard, press Reset button. (The additional mapping scheme is set to Default, but I have also tried VC #2005; neither fixed the problem.)
Tools, Import and Export Settings, re-import C# developer settings
devenv /reset
Using "repair" from the installer.
I know that I could probably fix just this one key binding by customizing it, but I don't want to do that. I want to reset all of the key binding spec to their default settings.
I figured out the problem: Ctrl + . was remapped by FSI when I installed F#. That's why resetting the key mappings didn't fix the issue: I still had F#. And the answer to which other mappings I've lost is, "Those mapped by FSI" (type FSI in keyboard mappings; there are only two).
I came across the same problem, (Tools-Options->Keyboard) View.ShowSmartTag is the field where you can re-assign the shortcut manually to Ctrl + .
I know it's a few months post date, but that should do the trick.
Do you have a "working" visual studio around? You can export the setting (keyboard only settings) from that machine and import it into your machine.
In the default Visual Studio 2008 C# key bindings, both Ctrl + . and Shift + Alt + F10 map to Show Smart Tag.
You can download Visual C# 2008 Keybinding Reference Poster here.
something that happen to me ...
make sure that "F lock" key on the keyboard (if you one of this) is on.. i didn't sew that i turn it off, and nothing work normal. (F5 - open the open dialog, F10 switch to split mode!)
Did you do something like install ReSharper?
If you did, you can fix this by going through your options for Visual Studio and/or the options for ReSharper (Can't remember now) and simply setting them up to continue using Visual Studio Layouts as opposed to that of the Add-in.

Resources