To remove old key bindings and/or restore Visual Studio key bindings overridden by the IntelliJ IDEA scheme, open Visual Studio options ( Tools | Options), go to Environment | Keyboard and click Reset. When you change a previously selected scheme, the key bindings set by the previous scheme are not canceled out. You can change the selected scheme later by using the corresponding selector on the Environment | Keyboard page of ReSharper options ( Alt+R, O). When you start Visual Studio for the first time after installing ReSharper, the Keyboard Scheme dialog opens, where you can choose the default shortcut scheme. Whatever scheme you choose, you can always change individual keyboard shortcuts later. It provides a common keyboard-centric experience among all JetBrains development environments. IntelliJ IDEA - This scheme shares the majority of shortcuts with those used in IntelliJ IDEA and its derivative web development IDEs. Visual Studio - This scheme aims to minimize conflicts with Visual Studio's own keyboard shortcuts. ReSharper provides two default keyboard shortcuts schemes.

For the rest of the actions, you can assign a preferred shortcut keys if needed. Most of the actions have default shortcuts, which you can use out of the box. Just be aware.All ReSharper actions can be invoked with keyboard shortcuts. Since I am using Ctrl+Shift+T for testing (that's just me) I did need to manually unbind it from New Tab in my Windows Terminal settings. Here's it in Animated Gif Form! (Using Carnac to see the hotkeys being pressed) LongDescription 'dotnet Test the current directory' ` Set-PSReadLineKeyHandler -Key Ctrl+Shift+t ` Here's Shift-Ctrl-T typing dotnet test and pressing enter. LongDescription 'dotnet Build the current directory' ` BriefDescription BuildCurrentDirectory ` Just add these to your $profile, after you've imported PSReadLine via if ($host.Name -eq 'ConsoleHost')īuilding with Shift-Ctrl-B Set-PSReadLineKeyHandler -Key Ctrl+Shift+b ` Here's Shift-Ctrl-B typing dotnet build and pressing enter. PSReadLine supports Set-PSReadLineKeyHandler which is basically hotkey bindings to any arbitrary script block.

So why not make a few of these intuitive hotkeys work for me there as well? I spend a lot of time at the command line, in Windows Terminal, in PowerShell, using PSReadLine.

It's built into my hands! Ctrl-Shift-T is test (even though it's non-standard, it's there, in my hands. When I want to build code I type Ctrl-Shift-B.

Visual studio hotkeys not working