When I used to work with add-ins, all add-in commands would show up as <Namespace.ClassName.MyCommand> under Tools|Options dialog, on Environment|Keyboard page. After moving to VSIP, my package commans show up under the menu they are added to. For instance, some of the Tools menu commands show up as <Tools.MyCommand> and some of the context menu commands show up as <Edit.MyCommand>.
Is there any way to group all of my VSIP package commands under a common category Ideally, I'd like to see all of my commands listed as <CompanyName.MyCommand>. BTW, my VSIP package is not a language package. This question applies to both VS 2003 and 2005.
I'd appreciate any help. Thanks.
How do I group VSIP package commands together?
Hot Topic
- how do i register my help as a plugin
- Experience report: Building my own DSL
- Problem Running VSTO on webserver - VSTOStorageWrapper.Interop.dll Seems to be missing
- Security seting problems on installing May CTP of LINQ
- Usage of WCF in commercial applications
- specify region's dataset at runtime
- MFP Package.Project source
- TOC & document map
- visual studio 2005 beta 2 installation problem
- Msbuild treat \r as \n ?
Visual Studio
- Visio diagram from vb.net
- VSS Security Setup
- Missing Database Project Template
- BUG: Scrollviewer problems with mouse events
- Excel Data Binding question
- Why can't show the Indigo Service Page?
- Port other than 80 for the Server Configuration
- Failed to create wizard.
- Class Details window (MSDN bug ID: FDBK24857)
- If I only work with Access Databases, what should I purchase
How do I group VSIP package commands together?
SiYuan
Thanks for the tip. For me, 6th parameter "Localized Canonical" worked as well but I tried it several ways, i.e. 5th parameter only, 5th and 6th, and 6th only.
Unfortunately, the end result is still not what I was after. My package adds several items to Tools menu. With your suggestion all of them show up as "Tools.Category.SubCategory.Command1". Is there any way to get rid of preceding menu name or is it basically works as designed
As I've mentioned earlier, with add-ins, commands show up nicely grouped as "Namespace.ClassName.MyCommand". That's what I'd ultimately like to get to.
I'd appreciate any other suggestions you might have.< xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" />
Rosiness
When you define your command in the CTC, you have six strings that can be supplied at the end of the button definition; string number five will overload the canonical name for the command. Supply the full path of the command like "Category.SubCategory.Command1", if you do not already supply strings for the prior slots, just add commas. Each empty slot will get a copy of slot 1 (button text)< xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" />
choon