PageRenderTime 31ms CodeModel.GetById 19ms RepoModel.GetById 0ms app.codeStats 0ms

/Visual Studio 2008/CSVSPackageWPFToolWindow/CSVSPackageWPFToolWindow.vsct

Unknown | 114 lines | 81 code | 33 blank | 0 comment | 0 complexity | 7ef8380a09505f00970a3dfa71143489 MD5 | raw file
  1. <?xml version="1.0" encoding="utf-8"?>
  2. <CommandTable xmlns="" xmlns:xs="">
  3. <!-- This is the file that defines the actual layout and type of the commands.
  4. It is divided in different sections (e.g. command definition, command
  5. placement, ...), with each defining a specific set of properties.
  6. See the comment before each section for more details about how to
  7. use it. -->
  8. <!-- The VSCT compiler (the tool that translates this file into the binary
  9. format that VisualStudio will consume) has the ability to run a preprocessor
  10. on the vsct file; this preprocessor is (usually) the C++ preprocessor, so
  11. it is possible to define includes and macros with the same syntax used
  12. in C++ files. Using this ability of the compiler here, we include some files
  13. defining some of the constants that we will use inside the file. -->
  14. <!--This is the file that defines the IDs for all the commands exposed by VisualStudio. -->
  15. <Extern href="stdidcmd.h"/>
  16. <!--This header contains the command ids for the menus provided by the shell. -->
  17. <Extern href="vsshlids.h"/>
  18. <!--Definition of some VSCT specific constants. In this sample we use it for the IDs inside the guidOfficeIcon group. -->
  19. <Extern href="msobtnid.h"/>
  20. <!--The Commands section is where we the commands, menus and menu groups are defined.
  21. This section uses a Guid to identify the package that provides the command defined inside it. -->
  22. <Commands package="guidVSPackageWPFToolWindowPkg">
  23. <!-- Inside this section we have different sub-sections: one for the menus, another
  24. for the menu groups, one for the buttons (the actual commands), one for the combos
  25. and the last one for the bitmaps used. Each element is identified by a command id that
  26. is a unique pair of guid and numeric identifier; the guid part of the identifier is usually
  27. called "command set" and is used to group different command inside a logically related
  28. group; your package should define its own command set in order to avoid collisions
  29. with command ids defined by other packages. -->
  30. <!-- In this section you can define new menu groups. A menu group is a container for
  31. other menus or buttons (commands); from a visual point of view you can see the
  32. group as the part of a menu contained between two lines. The parent of a group
  33. must be a menu. -->
  34. <Groups>
  35. </Groups>
  36. <!--Buttons section. -->
  37. <!--This section defines the elements the user can interact with, like a menu command or a button
  38. or combo box in a toolbar. -->
  39. <Buttons>
  40. <!--To define a menu group you have to specify its ID, the parent menu and its display priority.
  41. Some commands are not defined as shared, so they use our package CLSID as the command set GUID.
  42. Also, by specifying blank for the FLAGS, the command is default visible and enabled. Other valid
  44. These values for FLAGS can be or'ed together, e.g. "DEFAULTINVISIBLE | DYNAMICVISIBILITY"
  45. If you do not want an image next to your command, set the image to "guidOfficeIcon:msotcidNoIcon" -->
  46. <Button guid="guidVSPackageWPFToolWindowCmdSet" id="cmdidWPFToolWindow" priority="0x0100" type="Button">
  47. <Parent guid="guidSHLMainMenu" id="IDG_VS_WNDO_OTRWNDWS1"/>
  48. <Icon guid="guidImages" id="bmpPic2" />
  49. <Strings>
  50. <CommandName>cmdidWPFToolWindow</CommandName>
  51. <ButtonText>WPF Tool Window</ButtonText>
  52. </Strings>
  53. </Button>
  54. </Buttons>
  55. <!--The bitmaps section is used to define the bitmaps that are used for the commands.-->
  56. <Bitmaps>
  57. <!-- The bitmap id is defined in a way that is a little bit different from the others:
  58. the declaration starts with a guid for the bitmap strip, then there is the resource id of the
  59. bitmap strip containing the bitmaps and then there are the numeric ids of the elements used
  60. inside a button definition. An important aspect of this declaration is that the element id
  61. must be the actual index (1-based) of the bitmap inside the bitmap strip. -->
  62. <Bitmap guid="guidImages" href="Resources\Images_32bit.bmp" usedList="bmpPic1, bmpPic2, bmpPicSearch, bmpPicX, bmpPicArrows"/>
  63. </Bitmaps>
  64. </Commands>
  65. <Symbols>
  66. <!-- This is the package guid. -->
  67. <GuidSymbol name="guidVSPackageWPFToolWindowPkg" value="{31921cf1-2895-4725-aec7-a9c6f994018b}" />
  68. <!-- This is the guid used to group the menu commands together -->
  69. <GuidSymbol name="guidVSPackageWPFToolWindowCmdSet" value="{43ef812a-a984-4b42-b80a-98151b688722}">
  70. <IDSymbol name="MyMenuGroup" value="0x1020" />
  71. <IDSymbol name="cmdidWPFToolWindow" value="0x0101" />
  72. </GuidSymbol>
  73. <GuidSymbol name="guidImages" value="{81de379b-328a-4d5c-91e1-3111c17ef725}" >
  74. <IDSymbol name="bmpPic1" value="1" />
  75. <IDSymbol name="bmpPic2" value="2" />
  76. <IDSymbol name="bmpPicSearch" value="3" />
  77. <IDSymbol name="bmpPicX" value="4" />
  78. <IDSymbol name="bmpPicArrows" value="5" />
  79. </GuidSymbol>
  80. </Symbols>
  81. </CommandTable>