1. Start by creating a new project using the VSPackage Builder<\/b> template, located under Visual C# > Extensibility<\/b> in the new project dialog – then add a command to the empty extension by dragging an Add Command<\/b> quick start from the Toolbox onto the design surface. The result should be as shown.<\/p>\n<\/td>\n
2. Modify the command’s Button Text<\/b>, Command Flags<\/b>, Icon<\/b>, Name<\/b>, Priority<\/b> and Shortcut Keys<\/b> properties by selecting “Button1” on the design surface and making the appropriate edits using the property browser, as shown.<\/p>\n<\/td>\n <\/p>\n 3. Change the command placement location by clicking on the Location<\/b> property of the External Group<\/b> instance, and choosing an alternate (Tools Menu [Other 2]<\/b>). Note the long list of standard IDE locations that are available for selection.<\/p>\n<\/td>\n <\/p>\n <\/p>\n 4. Add another placement for the command by dragging a Group<\/b> from the External UI<\/b> category in the Toolbox onto the design surface and updating the Location<\/b> property as shown. Connect this new “external group” to the command using a Connect<\/b> control from the toolbox.<\/p>\n<\/td>\n <\/p>\n <\/p>\n 5. Now add a WPF-based toolwindow to the extension by dragging a ToolWindow (WPF)<\/b> from the Toolwindows<\/b> category in the toolbox onto the Toolwindow “swimlane” of the design surface. Connect the tool window to the command using a Launch<\/b> connection, as shown. The Launch connection causes the tool window to be opened whenever the command is executed.<\/p>\n<\/td>\n <\/p>\n <\/p>\n 6. Select the tool window instance on the design surface, and set the tool window properties as shown so that it will appear tabbed with the Solution Explorer when first opened.<\/p>\n<\/td>\n <\/p>\n <\/p>\n 7. Now drag a Toolwindow Toolbar<\/b>, Group<\/b> and Combo<\/b> from the toolbox onto the design surface and connect them and update their Name<\/b> properties as shown. By connecting the tool window toolbar to the tool window, it will automatically be displayed whenever the tool window is visible.<\/p>\n<\/td>\n <\/p>\n <\/p>\n 8. Save the solution, and press Ctrl-F5 to build and run the extension in the experimental instance. <\/p>\n Press Ctrl-Alt-1 to open the tool window (shown). Note that the new command is available on the Standard toolbar and in the Tools menu as expected.<\/p>\n<\/td>\n <\/p>\n Much more detail and two additional walkthroughs are included in the VSPackage Builder readme<\/a>. We highly recommend that prospective extension developers at least browse through the readme before embarking on their own VSPackage Builder based projects.<\/p>\n The VS 2010 SDK<\/a> includes the Visual Studio Package<\/b> project template that has for several years been the on ramp for developers building VSPackage<\/a>-based extensions. This template provides a solid extension starting point, however configuration changes such as adding and placing commands, must be handled through code changes in multiple files and involves a fairly steep learning curve. Feedback on this experience led to the definition of the key requirements for the VSPackage Builder project template, which included:<\/p>\n As implementation alternatives were explored, we quickly determined that the domain-specific language<\/a> based design surface approach leveraged by Feature Builder Power Tool<\/a>, could also be effective in helping to meet VSPackage Builder requirements. An exploration project was initiated with our friends at Clarius Consulting<\/a> doing much of the implementation heavy lifting, and the end result is VSPackage Builder v1.0 which is being made available for developers to try.<\/p>\n![\"clip_image002[13]\"](\"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-content\/uploads\/sites\/4\/2010\/09\/6138.clip_image00213_thumb_45C4EEAC-1.jpg\" "\\"clip_image002[13]\\"")
<\/a><\/p>\n<\/td>\n<\/tr>\n\n \n \n <\/a><\/p>\n<\/td>\n<\/tr>\n\n \n \n <\/a><\/p>\n<\/td>\n<\/tr>\n\n \n \n <\/a><\/p>\n<\/td>\n<\/tr>\n\n \n \n <\/a><\/p>\n<\/td>\n<\/tr>\n\n \n \n <\/a><\/p>\n<\/td>\n<\/tr>\n\n \n \n <\/a><\/p>\n<\/td>\n<\/tr>\n\n \n \n <\/a><\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\nMore Information<\/h3>\n
Background<\/h3>\n
\n
Sending Feedback<\/h3>\n