vsCommandStatusSupported | vsCommandStatusInvisible is not honored by a bug,
according to MS. See the last post of the thread:
http://groups.google.es/group/microsoft.public.vsnet.ide/tree/browse_frm/thread/
7f7bab1c295af16f/b0e0ece3ea2de809
As a workaround if you do NOT return vsCommandStatusSupported, the command
should remain invisible. In fact I think there was no need for the
vsCommandStatusInvisible flag...

Signature
Best regards,
Carlos J. Quintero
MZ-Tools: Productivity add-ins for Visual Studio
You can code, design and document much faster:
http://www.mztools.com
> Hello
>
[quoted text clipped - 15 lines]
> Thanks
> Dirk
dirk - 28 Sep 2006 14:48 GMT
And what should I return instead? I tried vsCommandStatusUnsupported and
also
making no assignment in cases where I would use vsCommandStatusInvisible.
This
does not work, it is always visible (gray).
I also found the thread you posted, but had hoped this only applies to VS
2003 and
were fixed in VS 2005.
Thanks
Dirk
> vsCommandStatusSupported | vsCommandStatusInvisible is not honored by a bug,
> according to MS. See the last post of the thread:
http://groups.google.es/group/microsoft.public.vsnet.ide/tree/browse_frm/thread/
7f7bab1c295af16f/b0e0ece3ea2de809
> As a workaround if you do NOT return vsCommandStatusSupported, the command
> should remain invisible. In fact I think there was no need for the
[quoted text clipped - 19 lines]
> > Thanks
> > Dirk
I was having similar issues. The reason that it never changes is because it is setup as a perm, rather then temp addin. See this article:
http://www.itpost.cn/en/1965/posts/196564142.shtml
Quick fix.
In OnConnection, add the command when:
connectMode = ext_ConnectMode.ext_cm_Startup
not
connectMode = ext_ConnectMode.ext_cm_UISetup
EggHeadCafe.com - .NET Developer Portal of Choice
http://www.eggheadcafe.com