Home Dashboard Directory Help

provide better error information in automation model (EnvDTE) for add-ins by Carlos J. Quintero


 as Won't Fix Help for as Won't Fix

Sign in
to vote
Type: Suggestion
ID: 469337
Opened: 6/23/2009 7:51:58 AM
Access Restriction: Public


When the following methods of the automation model (EnvDTE):

- EnvDTE.Commands.AddNamedCommand
- EnvDTE80.Commands2.AddNamedCommand
- EnvDTE80.Commands2.AddCommandBar
- VisualStudio.CommandBars.CommandBars.Add
- VisualStudio.CommandBars.CommandBar.Controls.Add

fail due to some problem with one of the parameters, they typically throw a System.ArgumentException "Value does not fall within the expected range.", but they don't provide the parameter that caused the problem or why it caused it.

See for example the poor exception information of this example:

Sign in to post a comment.
Posted by Microsoft on 8/6/2009 at 1:34 PM
Hello Carlos,

Thank you for taking the time to send us feedback on Visual Studio 2010 Beta 1.

I’ve spoken with developers on the Visual Studio Platform Shell team, and I found out that improving the error messages for those methods is not a simple fix. While we are all in complete agreement that we want to provide clear error messages for developers, in this case the change is too large for this point in the VS 2010 product cycle. (I would like to note that whenever it is non-trivial to do so, we do provide explanatory text with the error messages.)

Since we will not be able to improve these error messages in VS 2010, I will be resolving this bug as “Won’t Fix”. I will be making a note of this request in our feature backlog for future release planning. I will add a note that this bug has been rated highly by several individuals.

Thank you,
Suzanne Hansen, Program Manager, Visual Studio Platform Shell Team
Posted by Microsoft on 6/26/2009 at 12:29 PM
Hello CarlosQ,

Thank you for pointing out that we could improve the error messages for the DTE (automation model). We’ve assigned this bug to a developer on the Visual Studio Platform Shell team to investigate. If the change is low risk, we may be able to get this in to Visual Studio 2010. We will let you know the results of the developer’s investigation.

Thank you again for taking the time to report this issue.

Suzanne Hansen, Program Manager, Visual Studio Platform Shell Team
Posted by Microsoft on 6/23/2009 at 11:22 PM
Thank you for your feedback, we are currently reviewing the feedback you have submitted.
Sign in to post a workaround.