VSX开发：vsct文件综合示例——包含菜单、工具条、ToolWindow

2012/5/30 技术文章 0 Comment 12,279 Views

这里是用来做参考的一个综合vsct文件，希望对大家有帮助。同时欢迎有兴趣的朋友一起交流。

&lt;?xml version=&quot;1.0&quot; encoding=&quot;utf-8&quot;?&gt;
&lt;CommandTable xmlns=&quot;http://schemas.microsoft.com/VisualStudio/2005-10-18/CommandTable&quot; xmlns:xs=&quot;http://www.w3.org/2001/XMLSchema&quot;&gt;

  &lt;!--  This is the file that defines the actual layout and type of the commands.
        It is divided in different sections (e.g. command definition, command
        placement, ...), with each defining a specific set of properties.
        See the comment before each section for more details about how to
        use it. --&gt;

  &lt;!--  The VSCT compiler (the tool that translates this file into the binary 
        format that VisualStudio will consume) has the ability to run a preprocessor 
        on the vsct file; this preprocessor is (usually) the C++ preprocessor, so 
        it is possible to define includes and macros with the same syntax used 
        in C++ files. Using this ability of the compiler here, we include some files 
        defining some of the constants that we will use inside the file. --&gt;

  &lt;!--This is the file that defines the IDs for all the commands exposed by VisualStudio. --&gt;
  &lt;Extern href=&quot;stdidcmd.h&quot;/&gt;

  &lt;!--This header contains the command ids for the menus provided by the shell. --&gt;
  &lt;Extern href=&quot;vsshlids.h&quot;/&gt;

  &lt;!--Definition of some VSCT specific constants. In this sample we use it for the IDs inside the guidOfficeIcon group. --&gt;
  &lt;Extern href=&quot;msobtnid.h&quot;/&gt;


  &lt;!--Defines VK_INSERT --&gt;
  &lt;Extern href=&quot;virtkeys.h&quot;/&gt;
  



  &lt;!--The Commands section is where we the commands, menus and menu groups are defined.
      This section uses a Guid to identify the package that provides the command defined inside it. --&gt;
  &lt;Commands package=&quot;guidLupinAssistPkg&quot;&gt;
    &lt;!-- Inside this section we have different sub-sections: one for the menus, another  
    for the menu groups, one for the buttons (the actual commands), one for the combos 
    and the last one for the bitmaps used. Each element is identified by a command id that  
    is a unique pair of guid and numeric identifier; the guid part of the identifier is usually  
    called &quot;command set&quot; and is used to group different command inside a logically related  
    group; your package should define its own command set in order to avoid collisions  
    with command ids defined by other packages. --&gt;

    
    &lt;!--This is the sub-section that defines the menus and toolbars.--&gt;
    &lt;Menus&gt;
      &lt;!--  To define an element in this group you need an ID, a parent group, a display priority,
            a menu type, a name and a default text. --&gt;
      &lt;!--Common Toolbar --&gt;
      &lt;Menu guid=&quot;guidLupinAssistCmdSet&quot; id=&quot;IDM_TLB_RTF&quot; priority=&quot;0x0000&quot; type=&quot;Toolbar&quot;&gt;
        &lt;CommandFlag&gt;DefaultDocked&lt;/CommandFlag&gt;
        &lt;Strings&gt;
          &lt;ButtonText&gt;LupinAssist Toolbar&lt;/ButtonText&gt;
          &lt;CommandName&gt;LupinAssistToolbar&lt;/CommandName&gt;
        &lt;/Strings&gt;
      &lt;/Menu&gt;
      &lt;!-- Editor Context Menu --&gt;
      &lt;Menu guid=&quot;guidLupinAssistCmdSet&quot; id=&quot;IDMX_RTF&quot; priority=&quot;0x0000&quot; type=&quot;Context&quot;&gt;
        &lt;Parent guid=&quot;guidLupinAssistCmdSet&quot; id=&quot;0&quot;/&gt;
        &lt;Strings&gt;
          &lt;ButtonText&gt;LupinAssist Context Menu&lt;/ButtonText&gt;
          &lt;CommandName&gt;LupinAssistContextMenu&lt;/CommandName&gt;
        &lt;/Strings&gt;
      &lt;/Menu&gt;
      &lt;!--Main Menu--&gt;
      &lt;Menu guid=&quot;guidLupinAssistCmdSet&quot; id=&quot;IDM_TOPMENU&quot; priority=&quot;0x0000&quot; type=&quot;Menu&quot;&gt;
        &lt;Parent guid=&quot;guidSHLMainMenu&quot; id=&quot;IDG_VS_MM_PROJECT&quot; /&gt;
        &lt;Strings&gt;
          &lt;CommandName&gt;&amp;amp;LupinAssist&lt;/CommandName&gt;
          &lt;ButtonText&gt;LupinAssist&lt;/ButtonText&gt;
        &lt;/Strings&gt;
      &lt;/Menu&gt;
      &lt;Menu guid=&quot;guidLupinAssistCmdSet&quot; id=&quot;IDM_TOOLSMENUGROUP&quot; priority=&quot;0x0000&quot; type=&quot;Menu&quot;&gt;
        &lt;Parent guid=&quot;guidLupinAssistCmdSet&quot; id=&quot;TopMenuGroup&quot; /&gt;
        &lt;Strings&gt;
          &lt;CommandName&gt;&amp;amp;Tools&lt;/CommandName&gt;
          &lt;ButtonText&gt;LupinAssist&lt;/ButtonText&gt;
        &lt;/Strings&gt;
      &lt;/Menu&gt;
    &lt;/Menus&gt;
    
    &lt;!-- In this section you can define new menu groups. A menu group is a container for 
         other menus or buttons (commands); from a visual point of view you can see the 
         group as the part of a menu contained between two lines. The parent of a group 
         must be a menu. --&gt;
    &lt;Groups&gt;

      &lt;!--Menus--&gt;
      &lt;Group guid=&quot;guidLupinAssistCmdSet&quot; id=&quot;TopMenuGroup&quot; priority=&quot;0x0600&quot;&gt;
        &lt;Parent guid=&quot;guidLupinAssistCmdSet&quot; id=&quot;IDM_TOPMENU&quot;/&gt;
      &lt;/Group&gt;

      &lt;Group guid=&quot;guidLupinAssistCmdSet&quot; id=&quot;BottomMenuGroup&quot; priority=&quot;0x0601&quot;&gt;
        &lt;Parent guid=&quot;guidLupinAssistCmdSet&quot; id=&quot;IDM_TOPMENU&quot;/&gt;
      &lt;/Group&gt;

      &lt;Group guid=&quot;guidLupinAssistCmdSet&quot; id=&quot;ToolsMenuGroup&quot; priority=&quot;0x0602&quot;&gt;
        &lt;Parent guid=&quot;guidLupinAssistCmdSet&quot; id=&quot;IDM_TOOLSMENUGROUP&quot;/&gt;
      &lt;/Group&gt;

      &lt;!--Editor menu group --&gt;
      &lt;Group guid=&quot;guidLupinAssistCmdSet&quot; id=&quot;IDG_RTF_EDITOR_CMDS&quot; priority=&quot;0xFE00&quot;&gt;
        &lt;Parent guid=&quot;guidSHLMainMenu&quot; id=&quot;IDM_VS_MENU_EDIT&quot;/&gt;
      &lt;/Group&gt;

      &lt;!-- Toolbar groups --&gt;
      &lt;Group guid=&quot;guidLupinAssistCmdSet&quot; id=&quot;IDG_RTF_TLB_FONT1&quot; priority=&quot;0x0100&quot;&gt;
        &lt;Parent guid=&quot;guidLupinAssistCmdSet&quot; id=&quot;IDM_TLB_RTF&quot;/&gt;
      &lt;/Group&gt;
      &lt;Group guid=&quot;guidLupinAssistCmdSet&quot; id=&quot;IDG_RTF_TLB_FONT2&quot; priority=&quot;0x0200&quot;&gt;
        &lt;Parent guid=&quot;guidLupinAssistCmdSet&quot; id=&quot;IDM_TLB_RTF&quot;/&gt;
      &lt;/Group&gt;
      &lt;Group guid=&quot;guidLupinAssistCmdSet&quot; id=&quot;IDG_RTF_TLB_INDENT&quot; priority=&quot;0x0300&quot;&gt;
        &lt;Parent guid=&quot;guidLupinAssistCmdSet&quot; id=&quot;IDM_TLB_RTF&quot;/&gt;
      &lt;/Group&gt;
      &lt;Group guid=&quot;guidLupinAssistCmdSet&quot; id=&quot;IDG_RTF_TLB_BULLET&quot; priority=&quot;0x0400&quot;&gt;
        &lt;Parent guid=&quot;guidLupinAssistCmdSet&quot; id=&quot;IDM_TLB_RTF&quot;/&gt;
      &lt;/Group&gt;
      &lt;Group guid=&quot;guidLupinAssistCmdSet&quot; id=&quot;IDG_RTF_TLB_FONT_COMBOS&quot; priority=&quot;0x0040&quot;&gt;
        &lt;Parent guid=&quot;guidLupinAssistCmdSet&quot; id=&quot;IDM_TLB_RTF&quot;/&gt;
      &lt;/Group&gt;
      
      &lt;!--Context menu groups --&gt;
      &lt;Group guid=&quot;guidSHLMainMenu&quot; id=&quot;IDG_VS_EDIT_CUTCOPY&quot; priority=&quot;0x0100&quot;&gt;
        &lt;Parent guid=&quot;guidLupinAssistCmdSet&quot; id=&quot;IDMX_RTF&quot;/&gt;
      &lt;/Group&gt;
      &lt;Group guid=&quot;guidLupinAssistCmdSet&quot; id=&quot;IDG_RTF_CTX_PROPS&quot; priority=&quot;0x0200&quot;&gt;
        &lt;Parent guid=&quot;guidLupinAssistCmdSet&quot; id=&quot;IDMX_RTF&quot;/&gt;
      &lt;/Group&gt;
      &lt;Group guid=&quot;guidSharedMenuGroup&quot; id=&quot;IDG_VS_FORMAT_FONTFACE&quot; priority=&quot;0x0300&quot;&gt;
        &lt;Parent guid=&quot;guidLupinAssistCmdSet&quot; id=&quot;IDMX_RTF&quot;/&gt;
      &lt;/Group&gt;

    &lt;/Groups&gt;
    
    &lt;!--Buttons section. --&gt;
    &lt;!--This section defines the elements the user can interact with, like a menu command or a button 
        or combo box in a toolbar. --&gt;
    &lt;Buttons&gt;
      &lt;!--To define a menu group you have to specify its ID, the parent menu and its display priority. 
          The command is visible and enabled by default. If you need to change the visibility, status, etc, you can use
          the CommandFlag node.
          You can add more than one CommandFlag node e.g.:
              &lt;CommandFlag&gt;DefaultInvisible&lt;/CommandFlag&gt;
              &lt;CommandFlag&gt;DynamicVisibility&lt;/CommandFlag&gt;
          If you do not want an image next to your command, remove the Icon node or set it to &lt;Icon guid=&quot;guidOfficeIcon&quot; id=&quot;msotcidNoIcon&quot; /&gt; --&gt;                      
      &lt;Button guid=&quot;guidLupinAssistCmdSet&quot; id=&quot;cmdidSwitchCommand&quot; priority=&quot;0x0101&quot; type=&quot;Button&quot;&gt;
        &lt;Parent guid=&quot;guidLupinAssistCmdSet&quot; id=&quot;BottomMenuGroup&quot; /&gt;
        &lt;Icon guid=&quot;guidImages&quot; id=&quot;bmpPic1&quot; /&gt;
        &lt;Strings&gt;
          &lt;CommandName&gt;cmdidLupinCommand&lt;/CommandName&gt;
          &lt;ButtonText&gt;Enable/Disable LupinAssist&lt;/ButtonText&gt;
        &lt;/Strings&gt;
      &lt;/Button&gt;

      &lt;Button guid=&quot;guidLupinAssistCmdSet&quot; id=&quot;cmdidOptionsCommand&quot; priority=&quot;0x0102&quot; type=&quot;Button&quot;&gt;
        &lt;Parent guid=&quot;guidLupinAssistCmdSet&quot; id=&quot;BottomMenuGroup&quot; /&gt;
        &lt;Icon guid=&quot;guidImages&quot; id=&quot;bmpPicArrows&quot; /&gt;
        &lt;!--&lt;CommandFlag&gt;TextOnly&lt;/CommandFlag&gt;--&gt;
        &lt;Strings&gt;
          &lt;CommandName&gt;cmdidOptionsCommand&lt;/CommandName&gt;
          &lt;ButtonText&gt;&amp;amp;Options&lt;/ButtonText&gt;
        &lt;/Strings&gt;
      &lt;/Button&gt;

      &lt;!--子菜单--&gt;
      &lt;Button guid=&quot;guidLupinAssistCmdSet&quot; id=&quot;cmdidOptionToolWindow&quot; priority=&quot;0x0100&quot; type=&quot;Button&quot;&gt;
        &lt;Parent guid=&quot;guidLupinAssistCmdSet&quot; id=&quot;ToolsMenuGroup&quot;/&gt;
        &lt;Icon guid=&quot;guidImages&quot; id=&quot;bmpPic2&quot; /&gt;
        &lt;Strings&gt;
          &lt;CommandName&gt;cmdidOptionTool&lt;/CommandName&gt;
          &lt;ButtonText&gt;ToolWindow&lt;/ButtonText&gt;
        &lt;/Strings&gt;
      &lt;/Button&gt;

      &lt;Button guid=&quot;guidLupinAssistCmdSet&quot; id=&quot;cmdidToolBarCommand&quot;  priority=&quot;0x0100&quot; type=&quot;Button&quot;&gt;
        &lt;Parent guid=&quot;guidLupinAssistCmdSet&quot; id=&quot;ToolsMenuGroup&quot; /&gt;
        &lt;Strings&gt;
          &lt;CommandName&gt;cmdidLupinCommand&lt;/CommandName&gt;
          &lt;ButtonText&gt;Toolbars&lt;/ButtonText&gt;
        &lt;/Strings&gt;
      &lt;/Button&gt;


      &lt;Button guid=&quot;guidLupinAssistCmdSet&quot; id=&quot;commandIDStrike&quot; priority=&quot;0x0400&quot; type=&quot;Button&quot;&gt;
        &lt;Parent guid=&quot;guidSharedMenuGroup&quot; id=&quot;IDG_VS_FORMAT_FONTFACE&quot;/&gt;
        &lt;Icon guid=&quot;guidOfficeIcon&quot; id=&quot;msotcidStrikethrough&quot;/&gt;
        &lt;CommandFlag&gt;DefaultInvisible&lt;/CommandFlag&gt;
        &lt;CommandFlag&gt;DefaultDisabled&lt;/CommandFlag&gt;
        &lt;CommandFlag&gt;DynamicVisibility&lt;/CommandFlag&gt;
        &lt;Strings&gt;
          &lt;CommandName&gt;&amp;amp;Strike-through&lt;/CommandName&gt;
          &lt;CanonicalName&gt;Strike-through&lt;/CanonicalName&gt;
          &lt;ButtonText&gt;&amp;amp;Strike-through&lt;/ButtonText&gt;
          &lt;ToolTipText&gt;Strikes through text&lt;/ToolTipText&gt;
        &lt;/Strings&gt;
      &lt;/Button&gt;

    &lt;/Buttons&gt;
   
    &lt;!--The bitmaps section is used to define the bitmaps that are used for the commands.--&gt;
    &lt;Bitmaps&gt;
      &lt;!--  The bitmap id is defined in a way that is a little bit different from the others: 
            the declaration starts with a guid for the bitmap strip, then there is the resource id of the 
            bitmap strip containing the bitmaps and then there are the numeric ids of the elements used 
            inside a button definition. An important aspect of this declaration is that the element id 
            must be the actual index (1-based) of the bitmap inside the bitmap strip. --&gt;
      &lt;Bitmap guid=&quot;guidImages&quot; href=&quot;Resources\Images_32bit.bmp&quot; usedList=&quot;bmpPic1, bmpPic2, bmpPicSearch, bmpPicX, bmpPicArrows&quot;/&gt;

    &lt;/Bitmaps&gt;
 
  &lt;/Commands&gt;


  &lt;!--  Within this section you can specify the set of commands defined somewhere else that your  
        packages uses; for instance if your package uses the standard &lsquo;Copy&rsquo; command, you don&rsquo;t  
        need to define it, because it is defined by the shell, but you have to use this section  
        of the VSCT file to notify the shell that your package uses it using this section. --&gt;
  &lt;!--  Note that with combo boxes we have effectively two commands in one. Below 
        we have two pairs of commands; 1st pair commandIDFontName and commandIDFontNameHandler, 
        2nd pair commandIDFontSize and commandIDFontSizeHandler. Note that: 
        
        - commandIDFontName and commandIDFontSize handle the displaying and setting of the font 
          name and font size respectively 
        - commandIDFontNameHandler and commandIDFontSizeHandler fill the drop down menus 
          with the available font names and font sizes respectively 
     --&gt;
  &lt;!-- Note also that VS will call QueryStatus only on commandIDFontName and  
       commandIDFontSize, but not on cmdFontNameHandler and commandIDFontSizeHandler whereas 
       Exec will be called on all four commands. 
       Note also that Exec will be called for commandIDFontName and commandIDFontSize for 
       two cases; first to get the current font name or size and second to 
       set the font name or size whereas the Exec call for commandIDFontNameHandler and  
       commandIDFontSizeHandler always have the same meaning - fill the drop down menu. 
       Finally, note that placement for the combo boxes is defined in the combo 
       section below by the priority and not in the CommandPlacements section. --&gt;
  &lt;UsedCommands&gt;
    &lt;UsedCommand guid=&quot;guidVSStd97&quot; id=&quot;cmdidBold&quot;/&gt;
    &lt;UsedCommand guid=&quot;guidVSStd97&quot; id=&quot;cmdidItalic&quot;/&gt;
    &lt;UsedCommand guid=&quot;guidVSStd97&quot; id=&quot;cmdidUnderline&quot;/&gt;
    &lt;UsedCommand guid=&quot;guidVSStd97&quot; id=&quot;cmdidJustifyLeft&quot;/&gt;
    &lt;UsedCommand guid=&quot;guidVSStd97&quot; id=&quot;cmdidJustifyCenter&quot;/&gt;
    &lt;UsedCommand guid=&quot;guidVSStd97&quot; id=&quot;cmdidJustifyRight&quot;/&gt;
    &lt;UsedCommand guid=&quot;guidVSStd97&quot; id=&quot;cmdidFontName&quot;/&gt;
    &lt;UsedCommand guid=&quot;guidVSStd97&quot; id=&quot;cmdidFontSize&quot;/&gt;
    &lt;UsedCommand guid=&quot;guidVSStd97&quot; id=&quot;cmdidCut&quot;/&gt;
    &lt;UsedCommand guid=&quot;guidVSStd97&quot; id=&quot;cmdidCopy&quot;/&gt;
    &lt;UsedCommand guid=&quot;guidVSStd97&quot; id=&quot;cmdidPaste&quot;/&gt;
    &lt;UsedCommand guid=&quot;guidVSStd97&quot; id=&quot;cmdidDelete&quot;/&gt;
    &lt;UsedCommand guid=&quot;guidVSStd2K&quot; id=&quot;ECMD_INSERT&quot;/&gt;
    &lt;UsedCommand guid=&quot;guidVSStd2K&quot; id=&quot;ECMD_BULLETEDLIST&quot;/&gt;
  &lt;/UsedCommands&gt;
  
  &lt;!--Inside this section, we have the ability to place menu groups inside some other menu or 
      menu / commands inside other groups. 
      For instance, it is possible to place one of VisualStudio&#39;s menus or commands inside one of our  
      groups or one of our groups inside a menu defined somewhere else. --&gt;
  &lt;CommandPlacements&gt;
    &lt;!--Editor Toolbar --&gt;
    &lt;CommandPlacement guid=&quot;guidVSStd97&quot; id=&quot;cmdidFontName&quot; priority=&quot;0x0100&quot;&gt;
      &lt;Parent guid=&quot;guidLupinAssistCmdSet&quot; id=&quot;IDG_RTF_TLB_FONT_COMBOS&quot;/&gt;
    &lt;/CommandPlacement&gt;
    &lt;CommandPlacement guid=&quot;guidVSStd97&quot; id=&quot;cmdidFontSize&quot; priority=&quot;0x0200&quot;&gt;
      &lt;Parent guid=&quot;guidLupinAssistCmdSet&quot; id=&quot;IDG_RTF_TLB_FONT_COMBOS&quot;/&gt;
    &lt;/CommandPlacement&gt;
    &lt;CommandPlacement guid=&quot;guidVSStd97&quot; id=&quot;cmdidBold&quot; priority=&quot;0x0100&quot;&gt;
      &lt;Parent guid=&quot;guidLupinAssistCmdSet&quot; id=&quot;IDG_RTF_TLB_FONT1&quot;/&gt;
    &lt;/CommandPlacement&gt;
    &lt;CommandPlacement guid=&quot;guidVSStd97&quot; id=&quot;cmdidItalic&quot; priority=&quot;0x0200&quot;&gt;
      &lt;Parent guid=&quot;guidLupinAssistCmdSet&quot; id=&quot;IDG_RTF_TLB_FONT1&quot;/&gt;
    &lt;/CommandPlacement&gt;
    &lt;CommandPlacement guid=&quot;guidVSStd97&quot; id=&quot;cmdidUnderline&quot; priority=&quot;0x0300&quot;&gt;
      &lt;Parent guid=&quot;guidLupinAssistCmdSet&quot; id=&quot;IDG_RTF_TLB_FONT1&quot;/&gt;
    &lt;/CommandPlacement&gt;
    &lt;CommandPlacement guid=&quot;guidLupinAssistCmdSet&quot; id=&quot;commandIDStrike&quot; priority=&quot;0x0400&quot;&gt;
      &lt;Parent guid=&quot;guidLupinAssistCmdSet&quot; id=&quot;IDG_RTF_TLB_FONT1&quot;/&gt;
    &lt;/CommandPlacement&gt;
    &lt;CommandPlacement guid=&quot;guidVSStd97&quot; id=&quot;cmdidJustifyLeft&quot; priority=&quot;0x0100&quot;&gt;
      &lt;Parent guid=&quot;guidLupinAssistCmdSet&quot; id=&quot;IDG_RTF_TLB_INDENT&quot;/&gt;
    &lt;/CommandPlacement&gt;
    &lt;CommandPlacement guid=&quot;guidVSStd97&quot; id=&quot;cmdidJustifyCenter&quot; priority=&quot;0x0200&quot;&gt;
      &lt;Parent guid=&quot;guidLupinAssistCmdSet&quot; id=&quot;IDG_RTF_TLB_INDENT&quot;/&gt;
    &lt;/CommandPlacement&gt;
    &lt;CommandPlacement guid=&quot;guidVSStd97&quot; id=&quot;cmdidJustifyRight&quot; priority=&quot;0x0300&quot;&gt;
      &lt;Parent guid=&quot;guidLupinAssistCmdSet&quot; id=&quot;IDG_RTF_TLB_INDENT&quot;/&gt;
    &lt;/CommandPlacement&gt;
    &lt;CommandPlacement guid=&quot;guidVSStd2K&quot; id=&quot;ECMD_BULLETEDLIST&quot; priority=&quot;0x0100&quot;&gt;
      &lt;Parent guid=&quot;guidLupinAssistCmdSet&quot; id=&quot;IDG_RTF_TLB_BULLET&quot;/&gt;
    &lt;/CommandPlacement&gt;
    
    &lt;!-- Editor context menu --&gt;
    &lt;CommandPlacement guid=&quot;guidVSStd2K&quot; id=&quot;ECMD_BULLETEDLIST&quot; priority=&quot;0x0100&quot;&gt;
      &lt;Parent guid=&quot;guidLupinAssistCmdSet&quot; id=&quot;IDG_RTF_CTX_PROPS&quot;/&gt;
    &lt;/CommandPlacement&gt;
  &lt;/CommandPlacements&gt;



    &lt;!-- This section is where you can associate a command with a keyboard shortcut; this association is
      valid within a specific UI context, that is when the shell is inside a specific mode, e.g. during
      debugging, editing a file or when the user is using a specific designer. --&gt;
  &lt;!--&lt;VisibilityConstraints&gt;

    &lt;VisibilityItem guid=&quot;guidLupinAssistCmdSet&quot; id=&quot;IDM_TLB_RTF&quot; context=&quot;guidLupinAssistEditorFactory&quot; /&gt;
  &lt;/VisibilityConstraints&gt;--&gt;

  &lt;KeyBindings&gt;
     &lt;!--Keybindings 
       To define a binding, you have to specify the sequence of keys to press to activate the command  
       (keystate); 
       
       Notice that Visual Studio has a lot of components and commands, so it can be difficult to find a  
       key binding not used by somebody else; if the key bindings are conflicting only one will be used 
       and one problem is that the shell will not inform the user that a conflict was found. The only  
       way to detect the problem is to start Visual Studio under debugger, try to execute any command  
       and look if there is a message in the output window about a duplicated accelerator found.--&gt; 
    &lt;KeyBinding guid=&quot;guidVSStd97&quot; id=&quot;cmdidBold&quot; editor=&quot;guidLupinAssistEditorFactory&quot; key1=&quot;B&quot; mod1=&quot;Control&quot;/&gt;
    &lt;KeyBinding guid=&quot;guidVSStd97&quot; id=&quot;cmdidItalic&quot; editor=&quot;guidLupinAssistEditorFactory&quot; key1=&quot;I&quot; mod1=&quot;Control&quot;/&gt;
    &lt;KeyBinding guid=&quot;guidVSStd97&quot; id=&quot;cmdidUnderline&quot; editor=&quot;guidLupinAssistEditorFactory&quot; key1=&quot;U&quot; mod1=&quot;Control&quot;/&gt;
    &lt;KeyBinding guid=&quot;guidVSStd97&quot; id=&quot;cmdidJustifyLeft&quot; editor=&quot;guidLupinAssistEditorFactory&quot; key1=&quot;L&quot; mod1=&quot;Control&quot;/&gt;
    &lt;KeyBinding guid=&quot;guidVSStd97&quot; id=&quot;cmdidJustifyCenter&quot; editor=&quot;guidLupinAssistEditorFactory&quot; key1=&quot;E&quot; mod1=&quot;Control&quot;/&gt;
    &lt;KeyBinding guid=&quot;guidVSStd97&quot; id=&quot;cmdidJustifyRight&quot; editor=&quot;guidLupinAssistEditorFactory&quot; key1=&quot;R&quot; mod1=&quot;Control&quot;/&gt;
    &lt;KeyBinding guid=&quot;guidVSStd2K&quot; id=&quot;ECMD_INSERT&quot; editor=&quot;guidLupinAssistEditorFactory&quot; key1=&quot;VK_INSERT&quot;/&gt;
  &lt;/KeyBindings&gt;

  &lt;Symbols&gt;
    &lt;!-- This is the package guid. --&gt;
    &lt;GuidSymbol name=&quot;guidLupinAssistPkg&quot; value=&quot;{06e13938-3f41-49a3-bfe0-f6f6d2282a03}&quot; /&gt;
    
    &lt;!-- This is the guid used to group the menu commands together --&gt;
    &lt;GuidSymbol name=&quot;guidLupinAssistCmdSet&quot; value=&quot;{d21acfa5-eae6-495f-8739-7e7aa1541bab}&quot;&gt;

      &lt;IDSymbol name=&quot;IDM_TLB_RTF&quot; value=&quot;0x0001&quot; /&gt;
      &lt;IDSymbol name=&quot;IDMX_RTF&quot; value=&quot;0x0002&quot; /&gt;
      &lt;IDSymbol name=&quot;IDM_RTFMNU_ALIGN&quot; value=&quot;0x0004&quot; /&gt;
      &lt;IDSymbol name=&quot;IDM_RTFMNU_SIZE&quot; value=&quot;0x0005&quot; /&gt;
      &lt;IDSymbol name=&quot;IDM_TOPMENU&quot; value=&quot;0x0006&quot; /&gt;
      &lt;IDSymbol name=&quot;IDM_TOOLSMENUGROUP&quot; value=&quot;0x0007&quot; /&gt;        
      &lt;IDSymbol name=&quot;IDG_RTF_FMT_FONT1&quot; value=&quot;0x1000&quot; /&gt;
      &lt;IDSymbol name=&quot;IDG_RTF_FMT_FONT2&quot; value=&quot;0x1001&quot; /&gt;
      &lt;IDSymbol name=&quot;IDG_RTF_FMT_INDENT&quot; value=&quot;0x1002&quot; /&gt;
      &lt;IDSymbol name=&quot;IDG_RTF_FMT_BULLET&quot; value=&quot;0x1003&quot; /&gt;
      
      &lt;IDSymbol name=&quot;IDG_RTF_TLB_FONT1&quot; value=&quot;0x1004&quot; /&gt;
      &lt;IDSymbol name=&quot;IDG_RTF_TLB_FONT2&quot; value=&quot;0x1005&quot; /&gt;
      &lt;IDSymbol name=&quot;IDG_RTF_TLB_INDENT&quot; value=&quot;0x1006&quot; /&gt;
      &lt;IDSymbol name=&quot;IDG_RTF_TLB_BULLET&quot; value=&quot;0x1007&quot; /&gt;
      &lt;IDSymbol name=&quot;IDG_RTF_TLB_FONT_COMBOS&quot; value=&quot;0x1008&quot; /&gt;
      &lt;IDSymbol name=&quot;IDG_RTF_CTX_EDIT&quot; value=&quot;0x1009&quot; /&gt;
      &lt;IDSymbol name=&quot;IDG_RTF_CTX_PROPS&quot; value=&quot;0x100a&quot; /&gt;
      &lt;IDSymbol name=&quot;IDG_RTF_EDITOR_CMDS&quot; value=&quot;0x100b&quot; /&gt;
      &lt;IDSymbol name=&quot;TopMenuGroup&quot; value=&quot;0x1020&quot; /&gt;
      &lt;IDSymbol name=&quot;BottomMenuGroup&quot; value=&quot;0x1021&quot; /&gt;
      &lt;IDSymbol name=&quot;ToolsMenuGroup&quot; value=&quot;0x1022&quot; /&gt;
      &lt;IDSymbol name=&quot;cmdidSwitchCommand&quot; value=&quot;0x0100&quot; /&gt;
      &lt;IDSymbol name=&quot;cmdidOptionsCommand&quot; value=&quot;0x0101&quot; /&gt;
      &lt;IDSymbol name=&quot;cmdidOptionToolWindow&quot; value=&quot;0x0102&quot; /&gt;
      &lt;IDSymbol name=&quot;cmdidToolBarCommand&quot; value=&quot;0x103&quot; /&gt;
      &lt;IDSymbol name=&quot;commandIDStrike&quot; value=&quot;0x0104&quot; /&gt;
    &lt;/GuidSymbol&gt;
    
    &lt;GuidSymbol name=&quot;guidLupinAssistEditorFactory&quot; value=&quot;{0fcbb9b5-06c2-4a18-a21d-b787adedda42}&quot; /&gt;
    
    &lt;GuidSymbol name=&quot;guidImages&quot; value=&quot;{01c7d20a-85d5-449b-be64-37fd155ff694}&quot; &gt;
      &lt;IDSymbol name=&quot;bmpPic1&quot; value=&quot;1&quot; /&gt;
      &lt;IDSymbol name=&quot;bmpPic2&quot; value=&quot;2&quot; /&gt;
      &lt;IDSymbol name=&quot;bmpPicSearch&quot; value=&quot;3&quot; /&gt;
      &lt;IDSymbol name=&quot;bmpPicX&quot; value=&quot;4&quot; /&gt;
      &lt;IDSymbol name=&quot;bmpPicArrows&quot; value=&quot;5&quot; /&gt;
    &lt;/GuidSymbol&gt;
  &lt;/Symbols&gt;

&lt;/CommandTable&gt;

100

101

102

103

104

105

106

107

108

109

110

111

112

113

114

115

116

117

118

119

120

121

122

123

124

125

126

127

128

129

130

131

132

133

134

135

136

137

138

139

140

141

142

143

144

145

146

147

148

149

150

151

152

153

154

155

156

157

158

159

160

161

162

163

164

165

166

167

168

169

170

171

172

173

174

175

176

177

178

179

180

181

182

183

184

185

186

187

188

189

190

191

192

193

194

195

196

197

198

199

200

201

202

203

204

205

206

207

208

209

210

211

212

213

214

215

216

217

218

219

220

221

222

223

224

225

226

227

228

229

230

231

232

233

234

235

236

237

238

239

240

241

242

243

244

245

246

247

248

249

250

251

252

253

254

255

256

257

258

259

260

261

262

263

264

265

266

267

268

269

270

271

272

273

274

275

276

277

278

279

280

281

282

283

284

285

286

287

288

289

290

291

292

293

294

295

296

297

298

299

300

301

302

303

304

305

306

307

308

309

310

311

312

313

314

315

316

317

318

319

320

321

322

323

324

325

326

327

328

329

330

331

332

333

334

335

336

337

338

339

340

341

342

343

344

345

346

347

348

349

350

351

352

353

354

355

356

357

358

359

360

361

362

363

364

365

366

367

368

369

370

371

372

373

<?xml version="1.0" encoding="utf-8"?>

<!-- This is the file that defines the actual layout and type of the commands.

It is divided in different sections (e.g. command definition, command

placement, ...), with each defining a specific set of properties.

See the comment before each section for more details about how to

use it. -->

<!-- The VSCT compiler (the tool that translates this file into the binary

format that VisualStudio will consume) has the ability to run a preprocessor

on the vsct file; this preprocessor is (usually) the C++ preprocessor, so

it is possible to define includes and macros with the same syntax used

in C++ files. Using this ability of the compiler here, we include some files

defining some of the constants that we will use inside the file. -->

<!--The Commands section is where we the commands, menus and menu groups are defined.

This section uses a Guid to identify the package that provides the command defined inside it. -->

<!-- Inside this section we have different sub-sections: one for the menus, another

for the menu groups, one for the buttons (the actual commands), one for the combos

and the last one for the bitmaps used. Each element is identified by a command id that

is a unique pair of guid and numeric identifier; the guid part of the identifier is usually

called "command set" and is used to group different command inside a logically related

group; your package should define its own command set in order to avoid collisions

with command ids defined by other packages. -->

<Menus>

<!-- To define an element in this group you need an ID, a parent group, a display priority,

a menu type, a name and a default text. -->

<CommandFlag>DefaultDocked</CommandFlag>

<ButtonText>LupinAssist Toolbar</ButtonText>

<CommandName>LupinAssistToolbar</CommandName>

</Strings>

</Menu>

<ButtonText>LupinAssist Context Menu</ButtonText>

<CommandName>LupinAssistContextMenu</CommandName>

</Strings>

</Menu>

<CommandName>&amp;LupinAssist</CommandName>

<ButtonText>LupinAssist</ButtonText>

</Strings>

</Menu>

<CommandName>&amp;Tools</CommandName>

<ButtonText>LupinAssist</ButtonText>

</Strings>

</Menu>

</Menus>

<!-- In this section you can define new menu groups. A menu group is a container for

other menus or buttons (commands); from a visual point of view you can see the

group as the part of a menu contained between two lines. The parent of a group

must be a menu. -->

</Group>

</Group>

</Group>

</Group>

</Group>

</Group>

</Group>

</Group>

</Group>

</Group>

</Group>

</Group>

</Groups>

<!--This section defines the elements the user can interact with, like a menu command or a button

or combo box in a toolbar. -->

<!--To define a menu group you have to specify its ID, the parent menu and its display priority.

The command is visible and enabled by default. If you need to change the visibility, status, etc, you can use

the CommandFlag node.

You can add more than one CommandFlag node e.g.:

<CommandFlag>DefaultInvisible</CommandFlag>

<CommandFlag>DynamicVisibility</CommandFlag>

If you do not want an image next to your command, remove the Icon node or set it to <Icon guid="guidOfficeIcon" id="msotcidNoIcon" /> -->

<CommandName>cmdidLupinCommand</CommandName>

<ButtonText>Enable/Disable LupinAssist</ButtonText>

</Strings>

</Button>

<CommandName>cmdidOptionsCommand</CommandName>

<ButtonText>&amp;Options</ButtonText>

</Strings>

</Button>

<CommandName>cmdidOptionTool</CommandName>

<ButtonText>ToolWindow</ButtonText>

</Strings>

</Button>

<CommandName>cmdidLupinCommand</CommandName>

<ButtonText>Toolbars</ButtonText>

</Strings>

</Button>

<CommandFlag>DefaultInvisible</CommandFlag>

<CommandFlag>DefaultDisabled</CommandFlag>

<CommandFlag>DynamicVisibility</CommandFlag>

<CommandName>&amp;Strike-through</CommandName>

<CanonicalName>Strike-through</CanonicalName>

<ButtonText>&amp;Strike-through</ButtonText>

<ToolTipText>Strikes through text</ToolTipText>

</Strings>

</Button>

</Buttons>

<!-- The bitmap id is defined in a way that is a little bit different from the others:

the declaration starts with a guid for the bitmap strip, then there is the resource id of the

bitmap strip containing the bitmaps and then there are the numeric ids of the elements used

inside a button definition. An important aspect of this declaration is that the element id

must be the actual index (1-based) of the bitmap inside the bitmap strip. -->

</Bitmaps>

</Commands>

<!-- Within this section you can specify the set of commands defined somewhere else that your

packages uses; for instance if your package uses the standard ‘Copy’ command, you don’t

need to define it, because it is defined by the shell, but you have to use this section

of the VSCT file to notify the shell that your package uses it using this section. -->

<!-- Note that with combo boxes we have effectively two commands in one. Below

we have two pairs of commands; 1st pair commandIDFontName and commandIDFontNameHandler,

2nd pair commandIDFontSize and commandIDFontSizeHandler. Note that:

- commandIDFontName and commandIDFontSize handle the displaying and setting of the font

name and font size respectively

- commandIDFontNameHandler and commandIDFontSizeHandler fill the drop down menus

with the available font names and font sizes respectively

-->

<!-- Note also that VS will call QueryStatus only on commandIDFontName and

commandIDFontSize, but not on cmdFontNameHandler and commandIDFontSizeHandler whereas

Exec will be called on all four commands.

Note also that Exec will be called for commandIDFontName and commandIDFontSize for

two cases; first to get the current font name or size and second to

set the font name or size whereas the Exec call for commandIDFontNameHandler and

commandIDFontSizeHandler always have the same meaning - fill the drop down menu.

Finally, note that placement for the combo boxes is defined in the combo

section below by the priority and not in the CommandPlacements section. -->

</UsedCommands>

<!--Inside this section, we have the ability to place menu groups inside some other menu or

menu / commands inside other groups.

For instance, it is possible to place one of VisualStudio's menus or commands inside one of our

groups or one of our groups inside a menu defined somewhere else. -->

</CommandPlacement>

</CommandPlacement>

</CommandPlacement>

</CommandPlacement>

</CommandPlacement>

</CommandPlacement>

</CommandPlacement>

</CommandPlacement>

</CommandPlacement>

</CommandPlacement>

</CommandPlacement>

</CommandPlacements>

<!-- This section is where you can associate a command with a keyboard shortcut; this association is

valid within a specific UI context, that is when the shell is inside a specific mode, e.g. during

debugging, editing a file or when the user is using a specific designer. -->

<!--<VisibilityConstraints>

</VisibilityConstraints>-->

<!--Keybindings

To define a binding, you have to specify the sequence of keys to press to activate the command

(keystate);

Notice that Visual Studio has a lot of components and commands, so it can be difficult to find a

key binding not used by somebody else; if the key bindings are conflicting only one will be used

and one problem is that the shell will not inform the user that a conflict was found. The only

way to detect the problem is to start Visual Studio under debugger, try to execute any command

and look if there is a message in the output window about a duplicated accelerator found.-->

</KeyBindings>

</GuidSymbol>

</GuidSymbol>

</Symbols>

</CommandTable>

[……]

路平家的一亩三分地

VSX开发：vsct文件综合示例——包含菜单、工具条、ToolWindow

InstallShield12制作OCX或DLL安装包时碰到的问题

父母的电话

VS插件项目Failed to retrieve paths under VSTemplate for the specified registry hive.

NET-MVC模式下同名表单控件引发的错误

Punchfork创始人:创业者浪费精力的八个错误

今天的朝礼-道德经

互联网之最：Facebook IPO估值高达960亿美元

	选项1
	选项2

获取我的最新消息？