我想向服务器资源管理器中列出的SQL Server数据库中的每个表显示的每个节点的上下文菜单中添加一个自定义命令。在服务器资源管理器中为表节点创建Visual Studio扩展数据连接
我已经通过一个基本的教程了，并添加到工具菜单栏命令，以及自定义顶级菜单。
我也看到了教程Extending the Server Explorer to Display Web Parts，它非常接近我想要做的事情，但它是特定于SharePoint连接节点，并使用特定于Sharepoint的IExplorerNodeTypeExtension接口。我无法找到任何有关数据连接节点的文档。任何人都可以提供有关我应该利用哪些接口的相关文档或信息的任何参考？
随着Jack Zhai和其他一些网络资源的一些提示，我能够追踪到信息。
所以第一，我启用VSIPLogging由计算机\ HKEY_CURRENT_USER \ SOFTWARE \微软\ VisualStudio的### \一般
的EnableVSIPLogging设置为1
然后，我可以通过按住CTRL + SHIFT并右键单击它来确定Visual Studio中的任何菜单项或树节点的GUID和ID。
从这个，我能够确定与1283
命令ID，在服务器资源管理器中的顶级节点有{74D21310-2AEE-11D1-8BFB-00A0C90F26F7}的一个GUID在服务器浏览器对象节点（如表，存储过程，等等）有{d4f02a6a-c5ae-4bf2-938d-f1625bdca0e2}和33280（0x8200）一个指令id
对象节点父母在的一个GUID服务器资源管理器（例如静态“表”，“存储过程”，对对象节点进行分类的节点）具有{d4 f02a6a-c5ae-4bf2-938d-f1625bdca0e2}和命令ID 33024（0x8100）
因此，通过这些Guids，我现在可以将我的命令附加到我想要的位置。
我想要一个特定于单个表的命令，以及特定于数据库中所有表的命令，因此我将使用d4f02a6a-c5ae-4bf2-938d-f1625bdca0e2，命令标识为0x8200，Guid d4f02a6a-c5ae-4bf2-938d-f1625bdca0e2，命令ID为0x8100。
接下来，我需要在我的VSIX项目我vsct文件来定义这些值，所以我把它们添加到符号部分：
我加2个命令项目，我的项目，然后我需要更改组的父，使他们在服务器资源管理器上正确的区域出现：
现在，数据库命令时出现的所有静态对象的节点，即使我希望它只出现在“Tables”节点上，并且对于所有对象节点及其所有对象节点都会出现table命令，即使我希望它只出现在表节点本身中。我相信需要以某种方式在代码中解决问题，动态确定命令菜单项的可见性，但是我必须单独确定一个。
下面是整体的vsct：
<?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" />
<!--The Commands section is where 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="guidCRUDSPCommandsPackage">
<!-- 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>
<!-- Table scope -->
<Group guid="guidCRUDSPCommandsPackageCmdSet1" id="TableMenuGroup" priority="0x0600">
<!--<Parent guid="guidSHLMainMenu" id="IDM_VS_MENU_TOOLS" />-->
<Parent guid="guidServerExplorerObjectNode" id="IDMX_DV_OBJECT_NODE" />
</Group>
<!-- Database scope -->
<Group guid="guidCRUDSPCommandsPackageCmdSet1" id="DatabaseMenuGroup" priority="0x0600">
<!--<Parent guid="guidSHLMainMenu" id="IDM_VS_MENU_TOOLS" />-->
<Parent guid="guidServerExplorerObjectNode" id="IDMX_DV_STATIC_NODE" />
</Group>
</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.
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 /> -->
<Button guid="guidCRUDSPCommandsPackageCmdSet1" id="cmdidCmdTable" priority="0x0100" type="Button">
<Parent guid="guidCRUDSPCommandsPackageCmdSet1" id="TableMenuGroup" />
<Icon guid="guidImages" id="bmpPic1" />
<Strings>
<ButtonText>Command for Table</ButtonText>
</Strings>
</Button>
<Button guid="guidCRUDSPCommandsPackageCmdSet1" id="cmdidCmdDatabase" priority="0x0100" type="Button">
<Parent guid="guidCRUDSPCommandsPackageCmdSet1" id="DatabaseMenuGroup" />
<Icon guid="guidImages1" id="bmpPic1" />
<Strings>
<ButtonText>Command for Database</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\CmdTable.png" usedList="bmpPic1, bmpPic2, bmpPicSearch, bmpPicX, bmpPicArrows, bmpPicStrikethrough" />
<Bitmap guid="guidImages1" href="Resources\CmdDatabase.png" usedList="bmpPic1, bmpPic2, bmpPicSearch, bmpPicX, bmpPicArrows, bmpPicStrikethrough" />
</Bitmaps>
</Commands>
<Symbols>
<!-- {d4f02a6a-c5ae-4bf2-938d-f1625bdca0e2} is the object node in the server explorer -->
<GuidSymbol name="guidServerExplorerObjectNode" value="{d4f02a6a-c5ae-4bf2-938d-f1625bdca0e2}">
<!--server explorer - table-->
<IDSymbol name="IDMX_DV_OBJECT_NODE" value="0x8200" />
<IDSymbol name="IDMX_DV_STATIC_NODE" value="0x8100" />
</GuidSymbol>
<!-- {74D21310-2AEE-11D1-8BFB-00A0C90F26F7} is the server explorer -->
<GuidSymbol name="guidServerExplorer" value="{74D21310-2AEE-11D1-8BFB-00A0C90F26F7}">
<!--server explorer - table-->
<IDSymbol name="IDMX_DV_SERVER_NODE" value="0x503" />
</GuidSymbol>
<!-- This is the package guid. -->
<GuidSymbol name="guidCRUDSPCommandsPackage" value="{a71670bc-ef23-40a3-b8a0-ed872b79476c}" />
<!-- Constants-->
<GuidSymbol value="{946311de-35f2-4379-84e2-91867976faf8}" name="guidCRUDSPCommandsPackageCmdSet1">
<IDSymbol value="256" name="cmdidCmdTable" />
<IDSymbol value="257" name="cmdidCmdDatabase" />
<IDSymbol value="258" name="TableMenuGroup" />
<IDSymbol value="259" name="DatabaseMenuGroup" />
</GuidSymbol>
<GuidSymbol value="{679ecb35-41d9-4021-933b-ec6b25afc100}" name="guidImages">
<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" />
<IDSymbol name="bmpPicStrikethrough" value="6" />
</GuidSymbol>
<GuidSymbol value="{9392ca3d-3400-4b7a-a691-7108032249cd}" name="guidImages1">
<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" />
<IDSymbol name="bmpPicStrikethrough" value="6" />
</GuidSymbol>
</Symbols>
</CommandTable>
感谢您的分享，如果已解决，您可以将其标记为答案。祝你今天愉快。 –
您如何能够访问MenuItemCallback函数中每个对象的数据？ – user2531854
我还没有能够，那就是我的项目所在，因为我需要能够访问底层数据，或者以某种方式确定该节点代表什么表。 – Jeremy
就像卡洛斯·J的建议在这里：https://social.msdn.microsoft.com/Forums/vstudio/en-US/6e43cd5a-f0b1-4e05- 8dc8-f5509590e28f/server-explorer-extension？forum = vsx，似乎您需要使用EnableVSIPLogging在上下文菜单中找到组的Guid：Id。 –