EnvDTE.Command.Bindings causes Exception when setting value from a Visual Studio add-in - by Carlos J. Quintero

Status : 


Sign in
to vote
ID 761838 Comments
Status Closed Workarounds
Type Bug Repros 0
Opened 9/9/2012 11:55:09 AM
Access Restriction Public


In localized versions of Visual Studio, when an add-in retrieves the keyboard binding of a command that includes modifiers (Alt, Shift, Ctrl) and tries to assign it, a System.ArgumentException is thrown. It happens that the binding is returned with localized texts for the modifiers, but when assigning it only English texts for the modifiers are accepted.

This behavior is inconsistent and causes problems to add-ins that need to re-create commands and want to preserve keyboard bindings.

It affects to VS 2012, 2010, 2008 and 2005 at least.
Sign in to post a comment.
Posted by Microsoft on 11/13/2012 at 11:07 AM

Sorry about the delayed response and inconvenience. We do agree that this needs fixing. Unfortunately we are unable to address this for the current release. We have however, copied your suggestion to our product backlog and will bring it up during next version planning.

Visual Studio Platform Team
Posted by Carlos J. Quintero on 10/16/2012 at 1:13 AM
One scenario is this:

HOWTO: Prevent dead CommandBarButtons when Visual Studio or an add-in crashes.

Posted by Microsoft on 10/15/2012 at 10:50 AM

Thanks for your feedback. We'd like some more information to further investigate this issue. Could you provide some details on how you are using this in add-ins and what kidn of issues you are facing.

Thanks for your help investigating this issue.

Radhika Tadinada
Program Manager
Visual Studio Platform
Posted by Microsoft on 9/10/2012 at 2:48 AM
Thanks for your feedback.

We are rerouting this issue to the appropriate group within the Microsoft Visual Studio Connect Support Team for triage and resolution. These specialized experts will follow-up with your issue.
Posted by Microsoft on 9/9/2012 at 12:54 PM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)