5

This could be a generic question in terms of using different key maps between different versions of Visual Studio but especially relevant with ReSharper not supporting VS 2022 preview yet.

I have conflicts in common keybindings like Ctrl + T which maps to ReSharper GoTo in my existing Visual Studio 2019 with ReSharper installed. But in VS 2022, which seems to be using same keymaps, there is no ReSharper, so Ctrl + T does nothing.

If I reset keymap in VS 2022 to default so Ctrl + T maps to VS Edit.GotoAll that breaks my 2019 setup where it goes away from ReSharper to VS default (la 2022).

Is there a way to have completely separate keymap for each version? Or is there another way for me to work around this (something I am not configuring correctly etc.)

Thank you.

LazyOne
  • 158,824
  • 45
  • 388
  • 391
Senthil Ramanathan
  • 187
  • 1
  • 9

1 Answers1

3

Turn off your settings syncronization under Tools->Options...->Environment->Accounts:

enter image description here

Piers Myers
  • 10,611
  • 6
  • 46
  • 61
  • The option is already unticked in both 2019 and 2022. The situation is with the selection unticked. – Senthil Ramanathan Jun 20 '21 at 07:52
  • I would think that both versions of Visual Studio would have their own separate local vssettings files, mine for VS2019 is under: c:\Users\\AppData\Local\Microsoft\VisualStudio\16.0_xxx\Settings\CurrentSettings.vssettings - I don't have VS2022 installed so can't check which one it uses. – Piers Myers Jun 21 '21 at 14:01
  • I now have VS2022 and it seems that the options are linked to VS2019's. For example, changing the font or theme on one changes the other too. That setting I highlighted seems to have no impact. I have raised this as an issue with Microsoft. – Piers Myers Nov 17 '21 at 17:17