Visual Studio and .NET Framework Home
EnvDTE.Command.Delete does not remove CommandBarButtons created from that command on Visual Studio commandbars
Carlos J. Quintero
6/3/2009 6:40:31 AM
User(s) can reproduce this bug
When an add-in creates a Command and a CommandBarButton on a built-in Visual Studio commandbar, calling Command.Delete (when the add-in is unloaded) does not remove the CommandBarButton created from that command.
Visual Studio 2010 Beta 1
Windows XP Professional
Operating System Language
Steps to Reproduce
Using VS 2010 Beta 1, create a VB.NET add-in with the attached code. The add-in creates a command and a button on the "Standard" toolbar of Visual Studio.
Once loaded the add-in and created the button, go to the Tools, Add-in Manager and unload the add-in.
The button created on the "Standard" toolbar remains there.
If at this point you go to the Add-In Manager again to load the add-in again, an Exception happens.
When a Command is deleted, all the CommandBarButtons created from it on built-in Visual Studio commandbars should be removed. This was the behavior on previous versions of Visual Studio.
TAP Code (if applicable)
You can indicate your satisfaction with how Microsoft handled this issue by completing this quick
3 question survey
to post a comment.
Please enter a comment.
on 6/10/2009 at 4:09 PM
Thank you for reporting this bug, CarlosQ. I believe I have found and fixed the root cause of this issue, and the fix is currently being verified by our QA team.
Developer, Visual Studio Platform Shell
on 6/4/2009 at 8:05 PM
Thanks for your feedback.
We are escalating this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.
Visual Studio Product Team
to post a workaround.
Please enter a workaround.
© 2014 Microsoft