SUGGESTION: Do not overwrite existing Visual Studio key bindings on install

I find this one particularly annoying. Please provide an option to not
overwrite any keys already bound to commands in Visual Studio when I install
ReSharper. Some of the common commands that are rebound to ReSharper
commands are:

Run temporary macro (CTRLSHIFTP)
New file (CTRL+N)
Make uppercase (CTRLSHIFTU)
Debug processes (CTRLSHIFTP)



8 comments
Comment actions Permalink

Trust me, you'll use Ctrl-N for "Go to type" far more than you'll use "New
File". Rebind New-File to some other keystroke. Ctrl-N is a godsend, and I
miss it every day I can't use Resharper.

In fact, I cannot understand why VS2003/5 doesn't have this capability, or
how any developer gets any work done without it. It drives me NUTS to not
have Ctrl-N available.

"Nathan Alden" <a@a.com> wrote in message
news:dt3hqn$j3n$1@is.intellij.net...
>I find this one particularly annoying. Please provide an option to not

overwrite any keys already bound to commands in Visual Studio when I
install
ReSharper. Some of the common commands that are rebound to ReSharper
commands are:

>

Run temporary macro (CTRLSHIFTP)
New file (CTRL+N)
Make uppercase (CTRLSHIFTU)
Debug processes (CTRLSHIFTP)

>
>



0
Comment actions Permalink

And also you can easily restore the default keybindings by just switching
back to the Default keyboard mapping.

Regards,
Dmitry Shaporenkov
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

Trust me, you'll use Ctrl-N for "Go to type" far more than you'll use
"New File". Rebind New-File to some other keystroke. Ctrl-N is a
godsend, and I miss it every day I can't use Resharper.

In fact, I cannot understand why VS2003/5 doesn't have this
capability, or how any developer gets any work done without it. It
drives me NUTS to not have Ctrl-N available.

"Nathan Alden" <a@a.com> wrote in message
news:dt3hqn$j3n$1@is.intellij.net...

>> I find this one particularly annoying. Please provide an option to
>> not
>> overwrite any keys already bound to commands in Visual Studio when I
>> install
>> ReSharper. Some of the common commands that are rebound to ReSharper
>> commands are:
>> Run temporary macro (CTRLSHIFTP)
>> New file (CTRL+N)
>> Make uppercase (CTRLSHIFTU)
>> Debug processes (CTRLSHIFTP)


0
Comment actions Permalink

The problem with switching to the default bindings is that I lose other
custom bindings I had configured after originally installing Visual Studio
(such as bindings to my own macros).

"Dmitry Shaporenkov (JetBrains)" <dsha@jetbrains.com> wrote in message
news:c8a894d91059f58c8021d20299fad@news.intellij.net...

And also you can easily restore the default keybindings by just switching
back to the Default keyboard mapping.

>

Regards,
Dmitry Shaporenkov
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

>
>> Trust me, you'll use Ctrl-N for "Go to type" far more than you'll use
>> "New File". Rebind New-File to some other keystroke. Ctrl-N is a
>> godsend, and I miss it every day I can't use Resharper.
>>
>> In fact, I cannot understand why VS2003/5 doesn't have this
>> capability, or how any developer gets any work done without it. It
>> drives me NUTS to not have Ctrl-N available.
>>
>> "Nathan Alden" <a@a.com> wrote in message
>> news:dt3hqn$j3n$1@is.intellij.net...
>>
>>> I find this one particularly annoying. Please provide an option to
>>> not
>>> overwrite any keys already bound to commands in Visual Studio when I
>>> install
>>> ReSharper. Some of the common commands that are rebound to ReSharper
>>> commands are:
>>> Run temporary macro (CTRLSHIFTP)
>>> New file (CTRL+N)
>>> Make uppercase (CTRLSHIFTU)
>>> Debug processes (CTRLSHIFTP)
>



0
Comment actions Permalink

Can't you save off your existing key bindings before installing resharper?

Then of course, you'd have to manually map any resharper features to keys
you wanted afterwords... which would probably be almost as much work as just
doing the necessary remappings after installing resharper over your existing
key mappings.

I really don't think there's a satisfactory solution for everyone here, or
even any real compelling options.

I know the guys at JetBrains chose the keys they did because they're similar
to the key mappings used in their IDEA Java IDE, which of course eases
transition for those of us who have used IDEA previously in the Java world,
or for those who jump back and forth between Java and C#.

All I can suggest is to give the new bindings a chance, and remap those that
you feel you can't get used to. But a lot of us on these forums refer to
features by their keystroke (such as "I use Ctrl-N all the time... I love
it!") so be prepared for that level of confusion.


"Nathan Alden" <visualcsharpcoder@hotmail.com> wrote in message
news:dt54k0$5oq$1@is.intellij.net...

The problem with switching to the default bindings is that I lose other
custom bindings I had configured after originally installing Visual Studio
(such as bindings to my own macros).

>

"Dmitry Shaporenkov (JetBrains)" <dsha@jetbrains.com> wrote in message
news:c8a894d91059f58c8021d20299fad@news.intellij.net...

>> And also you can easily restore the default keybindings by just switching
>> back to the Default keyboard mapping.
>>
>> Regards,
>> Dmitry Shaporenkov
>> JetBrains, Inc
>> http://www.jetbrains.com
>> "Develop with pleasure!"
>>
>>> Trust me, you'll use Ctrl-N for "Go to type" far more than you'll use
>>> "New File". Rebind New-File to some other keystroke. Ctrl-N is a
>>> godsend, and I miss it every day I can't use Resharper.
>>>
>>> In fact, I cannot understand why VS2003/5 doesn't have this
>>> capability, or how any developer gets any work done without it. It
>>> drives me NUTS to not have Ctrl-N available.
>>>
>>> "Nathan Alden" <a@a.com> wrote in message
>>> news:dt3hqn$j3n$1@is.intellij.net...
>>>
>>>> I find this one particularly annoying. Please provide an option to
>>>> not
>>>> overwrite any keys already bound to commands in Visual Studio when I
>>>> install
>>>> ReSharper. Some of the common commands that are rebound to ReSharper
>>>> commands are:
>>>> Run temporary macro (CTRLSHIFTP)
>>>> New file (CTRL+N)
>>>> Make uppercase (CTRLSHIFTU)
>>>> Debug processes (CTRLSHIFTP)
>>
>>
>



0
Comment actions Permalink

Maybe, but I find Ctrl-N is nicely intuitive for New File whereas Ctrl-N for
Go to type is completely unintuitive. I usually work around the solution by
setting my keystroke shortcuts to when installing ReSharper, which
prevents ReSharper's shortcuts from installing and overwriting my own
default. I prefer to bind ReSharper's shortcuts with a Ctrl-R prefix to keep
them separate and somewhat more intuitive (e.g. Ctrl-R+Ctrl-E to encapsulate
field or Ctrl-R+Ctr-X to extract method).

Perhaps a work-around would be to create the shortcuts under a ReSharper
mapping name instead of overwriting existing shortcuts or to save the
shortcuts to a binding file that we can modify and import.



"Paul Bradshaw" <pbradshaw@advsol.com> wrote in message
news:dt4uee$8v5$1@is.intellij.net...

Trust me, you'll use Ctrl-N for "Go to type" far more than you'll use "New
File". Rebind New-File to some other keystroke. Ctrl-N is a godsend, and
I miss it every day I can't use Resharper.

>

In fact, I cannot understand why VS2003/5 doesn't have this capability, or
how any developer gets any work done without it. It drives me NUTS to not
have Ctrl-N available.

>

"Nathan Alden" <a@a.com> wrote in message
news:dt3hqn$j3n$1@is.intellij.net...

>>I find this one particularly annoying. Please provide an option to not
>> overwrite any keys already bound to commands in Visual Studio when I
>> install
>> ReSharper. Some of the common commands that are rebound to ReSharper
>> commands are:
>>
>> Run temporary macro (CTRLSHIFTP)
>> New file (CTRL+N)
>> Make uppercase (CTRLSHIFTU)
>> Debug processes (CTRLSHIFTP)
>>
>>
>>
>



0
Comment actions Permalink

I think that is the most annoying in Resharper under VS 2005. I do not like
creating my own binding schema. It takes too much time to recondigure each
application every time you either get new windows or profile or have to work
on just another VM.

Maybe, but I find Ctrl-N is nicely intuitive for New File whereas
Ctrl-N for Go to type is completely unintuitive. I usually work around
the solution by setting my keystroke shortcuts to when
installing ReSharper, which prevents ReSharper's shortcuts from
installing and overwriting my own default. I prefer to bind
ReSharper's shortcuts with a Ctrl-R prefix to keep them separate and
somewhat more intuitive (e.g. Ctrl-R+Ctrl-E to encapsulate field or
Ctrl-R+Ctr-X to extract method).

Perhaps a work-around would be to create the shortcuts under a
ReSharper mapping name instead of overwriting existing shortcuts or to
save the shortcuts to a binding file that we can modify and import.

"Paul Bradshaw" <pbradshaw@advsol.com> wrote in message
news:dt4uee$8v5$1@is.intellij.net...

>> Trust me, you'll use Ctrl-N for "Go to type" far more than you'll use
>> "New File". Rebind New-File to some other keystroke. Ctrl-N is a
>> godsend, and I miss it every day I can't use Resharper.
>>
>> In fact, I cannot understand why VS2003/5 doesn't have this
>> capability, or how any developer gets any work done without it. It
>> drives me NUTS to not have Ctrl-N available.
>>
>> "Nathan Alden" <a@a.com> wrote in message
>> news:dt3hqn$j3n$1@is.intellij.net...
>>
>>> I find this one particularly annoying. Please provide an option to
>>> not
>>> overwrite any keys already bound to commands in Visual Studio when I
>>> install
>>> ReSharper. Some of the common commands that are rebound to ReSharper
>>> commands are:
>>> Run temporary macro (CTRLSHIFTP)
>>> New file (CTRL+N)
>>> Make uppercase (CTRLSHIFTU)
>>> Debug processes (CTRLSHIFTP)


0
Comment actions Permalink

Hello Yuriy,

in cases you mentioned you anyway need to either copy all settings from files
they were saved to or set them manually.
I doubt that this is a frequent and common situation.

Regards,
Dmitry Shaporenkov
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

I think that is the most annoying in Resharper under VS 2005. I do
not like creating my own binding schema. It takes too much time to
recondigure each application every time you either get new windows or
profile or have to work on just another VM.

>> Maybe, but I find Ctrl-N is nicely intuitive for New File whereas
>> Ctrl-N for Go to type is completely unintuitive. I usually work
>> around the solution by setting my keystroke shortcuts to
>> when installing ReSharper, which prevents ReSharper's shortcuts from
>> installing and overwriting my own default. I prefer to bind
>> ReSharper's shortcuts with a Ctrl-R prefix to keep them separate and
>> somewhat more intuitive (e.g. Ctrl-R+Ctrl-E to encapsulate field or
>> Ctrl-R+Ctr-X to extract method).
>>
>> Perhaps a work-around would be to create the shortcuts under a
>> ReSharper mapping name instead of overwriting existing shortcuts or
>> to save the shortcuts to a binding file that we can modify and
>> import.
>>
>> "Paul Bradshaw" <pbradshaw@advsol.com> wrote in message
>> news:dt4uee$8v5$1@is.intellij.net...
>>
>>> Trust me, you'll use Ctrl-N for "Go to type" far more than you'll
>>> use "New File". Rebind New-File to some other keystroke. Ctrl-N is
>>> a godsend, and I miss it every day I can't use Resharper.
>>>
>>> In fact, I cannot understand why VS2003/5 doesn't have this
>>> capability, or how any developer gets any work done without it. It
>>> drives me NUTS to not have Ctrl-N available.
>>>
>>> "Nathan Alden" <a@a.com> wrote in message
>>> news:dt3hqn$j3n$1@is.intellij.net...
>>>> I find this one particularly annoying. Please provide an option to
>>>> not
>>>> overwrite any keys already bound to commands in Visual Studio when
>>>> I
>>>> install
>>>> ReSharper. Some of the common commands that are rebound to
>>>> ReSharper
>>>> commands are:
>>>> Run temporary macro (CTRLSHIFTP)
>>>> New file (CTRL+N)
>>>> Make uppercase (CTRLSHIFTU)
>>>> Debug processes (CTRLSHIFTP)


0

Please sign in to leave a comment.