/Visual Studio 2008/CSVSPackageWPFToolWindow/CSVSPackageWPFToolWindow.vsct
Unknown | 114 lines | 81 code | 33 blank | 0 comment | 0 complexity | 7ef8380a09505f00970a3dfa71143489 MD5 | raw file
- <?xml version="1.0" encoding="utf-8"?>
- <CommandTable xmlns="http://schemas.microsoft.com/VisualStudio/2005-10-18/CommandTable" xmlns:xs="http://www.w3.org/2001/XMLSchema">
-
- <!-- 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. -->
-
- <!--This is the file that defines the IDs for all the commands exposed by VisualStudio. -->
- <Extern href="stdidcmd.h"/>
-
- <!--This header contains the command ids for the menus provided by the shell. -->
- <Extern href="vsshlids.h"/>
-
- <!--Definition of some VSCT specific constants. In this sample we use it for the IDs inside the guidOfficeIcon group. -->
- <Extern href="msobtnid.h"/>
-
-
-
-
-
- <!--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. -->
- <Commands package="guidVSPackageWPFToolWindowPkg">
- <!-- 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. -->
-
-
- <!-- 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. -->
- <Groups>
-
-
-
-
- </Groups>
-
- <!--Buttons section. -->
- <!--This section defines the elements the user can interact with, like a menu command or a button
- or combo box in a toolbar. -->
- <Buttons>
- <!--To define a menu group you have to specify its ID, the parent menu and its display priority.
- Some commands are not defined as shared, so they use our package CLSID as the command set GUID.
- Also, by specifying blank for the FLAGS, the command is default visible and enabled. Other valid
- values for FLAGS are the following: DEFAULTDISABLED, DEFAULTINVISIBLE, DYNAMICVISIBILITY, TEXTCHANGES
-
- These values for FLAGS can be or'ed together, e.g. "DEFAULTINVISIBLE | DYNAMICVISIBILITY"
- If you do not want an image next to your command, set the image to "guidOfficeIcon:msotcidNoIcon" -->
-
-
- <Button guid="guidVSPackageWPFToolWindowCmdSet" id="cmdidWPFToolWindow" priority="0x0100" type="Button">
- <Parent guid="guidSHLMainMenu" id="IDG_VS_WNDO_OTRWNDWS1"/>
- <Icon guid="guidImages" id="bmpPic2" />
- <Strings>
- <CommandName>cmdidWPFToolWindow</CommandName>
- <ButtonText>WPF Tool Window</ButtonText>
- </Strings>
- </Button>
-
-
- </Buttons>
-
- <!--The bitmaps section is used to define the bitmaps that are used for the commands.-->
- <Bitmaps>
- <!-- 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. -->
- <Bitmap guid="guidImages" href="Resources\Images_32bit.bmp" usedList="bmpPic1, bmpPic2, bmpPicSearch, bmpPicX, bmpPicArrows"/>
-
- </Bitmaps>
-
- </Commands>
-
-
- <Symbols>
- <!-- This is the package guid. -->
- <GuidSymbol name="guidVSPackageWPFToolWindowPkg" value="{31921cf1-2895-4725-aec7-a9c6f994018b}" />
-
- <!-- This is the guid used to group the menu commands together -->
- <GuidSymbol name="guidVSPackageWPFToolWindowCmdSet" value="{43ef812a-a984-4b42-b80a-98151b688722}">
-
- <IDSymbol name="MyMenuGroup" value="0x1020" />
- <IDSymbol name="cmdidWPFToolWindow" value="0x0101" />
- </GuidSymbol>
-
-
-
- <GuidSymbol name="guidImages" value="{81de379b-328a-4d5c-91e1-3111c17ef725}" >
- <IDSymbol name="bmpPic1" value="1" />
- <IDSymbol name="bmpPic2" value="2" />
- <IDSymbol name="bmpPicSearch" value="3" />
- <IDSymbol name="bmpPicX" value="4" />
- <IDSymbol name="bmpPicArrows" value="5" />
- </GuidSymbol>
- </Symbols>
-
- </CommandTable>