CommandBarPopup.Visible = False doesn't work when CommandBarPopup in context menu - by Carlos J. Quintero

Status : 

  Deferred<br /><br />
		The product team has reviewed this issue and has deferred it for consideration at a later time.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.


1
0
Sign in
to vote
ID 758545 Comments
Status Closed Workarounds
Type Bug Repros 0
Opened 8/17/2012 11:09:52 AM
Access Restriction Public

Description

In an add-in that creates a CommandBarPopup in a context menu (for example, in the code window context menu), if you set the CommandBarPopup.Visible property to false, it is ignored. However, if the CommandBarPopup in on a toolbar, it works as expected.

This bug was introduced by VS 2010 and still exists in VS 2012. It didn't happen in VS 2008 or 2005.
Sign in to post a comment.
Posted by Radhika [MSFT] on 10/31/2012 at 2:33 PM
Hi,

Thanks for that information. We have copied your suggestion to our product backlog and will bring it up during next version planning.

Thanks,
Radhika Tadinada
Program Manager
Visual Studio Platform
Posted by Carlos J. Quintero on 10/12/2012 at 1:18 AM
My MZ-Tools 7.0 add-in (www.mztools.com) adds some menu entries to the context menu of a code window. Some of these entries are CommandbarPopups, not CommandbarButtons. See attached image.

On the other hand, I provide an Options window (see attached image) where the user can select which menu entries (CommandbarPopups or CommandbarButtons) are visible or not.

So, the add-in may need to set the CommandBarPopup.Visible property to false, and this fails for CommandBarPopups on context menus of VS 2010 and 2012. But this worked on VS 2005 and 2008, and it works on VS 2010 and 2012 if the CommandBarPopup is on a toolbar rather than on a context menu.
Posted by Radhika [MSFT] on 10/11/2012 at 5:51 PM
Hi,

Thanks for the feedback. Unfortunately, at this stage in the product cycle we are unable to address this for the current release as we are only taking critical bug fixes. We have copied your suggestion to our product backlog and will bring it up during next version planning.

We'd like to better understand the scenario, could you provide some details.

Thanks,
Radhika Tadinada
Program Manager
Visual Studio Platform
Posted by Pengzhen [MSFT] on 8/20/2012 at 5:15 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 Helen [MSFT] on 8/17/2012 at 11:52 AM
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)