blocks|key|813317|text|EnableVSIPLogging注册表值仍然适用于VS+2015。您只需在HKEY_CURRENT_USER\SOFTWARE\Microsoft\VisualStudio\14.0\General.下添加一个设置为1的EnableVSIPLogging+DWORD值|type|unstyled|depth|inlineStyleRanges|entityRanges|data|813318|如果CTRL%2BSHIFT+%2B菜单弹出或菜单选择没有产生该对话框，则可能是有问题的菜单项没有作为VSCT资源实现。|813319|也就是说，您可能需要尝试一下，因为编辑器和设计器不需要使用与代码编辑器相同的上下文菜单。|813320|此外，您可能想在https://visualstudiogallery.msdn.microsoft.com/ab39a092-1343-46e2-b0f1-6a3f91155aa6+(2017)或https://marketplace.visualstudio.com/items?itemName=MadsKristensen.ExtensibilityEssentials2019+(2019)上尝试Mads“可扩展性工具”扩展。|offset|length|813321|他为VSCT文件添加了一个很好的自动补全功能，非常有用。|813322|entityMap|0|LINK|mutability|MUTABLE|url|https://visualstudiogallery.msdn.microsoft.com/ab39a092-1343-46e2-b0f1-6a3f91155aa6|1|https://marketplace.visualstudio.com/items?itemName=MadsKristensen.ExtensibilityEssentials2019^0|0|0|0|8|2B|0|2R|2M|1|0|0^^$0|@$1|2|3|4|5|6|7|V|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|W|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|X|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|Y|8|@]|9|@$H|Z|I|10|1|11]|$H|12|I|13|1|14]]|A|$]]|$1|J|3|K|5|6|7|15|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|16|8|@]|9|@]|A|$]]]|M|$N|$5|O|P|Q|A|$R|S]]|T|$5|O|P|Q|A|$R|U]]]]

The EnableVSIPLogging registry value still works for VS 2015. You just need to add an EnableVSIPLogging DWORD set to 1, under HKEY_CURRENT_USER\SOFTWARE\Microsoft\VisualStudio\14.0\General.
If the CTRL+SHIFT + menu popup or menu select, doesn't result in that dialog, chances are the menu item in question is not implemented as a VSCT resource.
That being said, you may need to experiment a little, as editor and designers are not required to use the same context menu that the code editor uses.
Also, you might want to try out Mads &quot;Extensibility Tools&quot; extension at <a href="https://visualstudiogallery.msdn.microsoft.com/ab39a092-1343-46e2-b0f1-6a3f91155aa6" rel="nofollow noreferrer">https://visualstudiogallery.msdn.microsoft.com/ab39a092-1343-46e2-b0f1-6a3f91155aa6</a> (2017) or <a href="https://marketplace.visualstudio.com/items?itemName=MadsKristensen.ExtensibilityEssentials2019" rel="nofollow noreferrer">https://marketplace.visualstudio.com/items?itemName=MadsKristensen.ExtensibilityEssentials2019</a> (2019).
He's added a nice autocomplete for VSCT files that's pretty useful.

blocks|key|813405|text|我能够为上下文菜单找出正确的命令组。事实证明，各种编辑器都使用单独的上下文It，因此必须作为单独的菜单进行管理，因此很快就会变得混乱。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|813406|步骤|offset|length|style|BOLD|813407|813408|I使用HKEY_CURRENT_USER\SOFTWARE\Microsoft\VisualStudio\14.0\General键和EnableVSIPLogging值1启用日志记录。|ordered-list-item|CODE|813409|I随后导航到编辑器，将鼠标放在空白区域上，按CTRL-SHIFT组合键，然后右键单击鼠标|813410|813411|这为信息提供了一个类似于menu+group的信息，它看起来像这样：|813412|---------------------------
VSDebug+Message
---------------------------
Menu+data:
++++Guid+=+{D7E8C5E1-BDB8-11D0-9C88-0000F8040A53}
++++GuidID+=+358
++++CmdID+=+53
++++Type+=+0x00000400
++++Flags+=+0x00000000
++++NameLoc+=+ASPX+Context
---------------------------
OK+++
---------------------------|code-block|syntax|javascript|813413|重要的值是GUID和CommandID。|813414|像这样在Symbols下添加Guid和命令ID，以注册将Guid映射到CommandSet和将CommandId映射到上下文菜单值的命令集：|813415|<GuidSymbol+name="aspxContextCommandSet"+value="{D7E8C5E1-BDB8-11D0-9C88-0000F8040A53}">
++<IDSymbol+name="aspxContextMenu"+value="0x0035"/>
</GuidSymbol>|813416|请注意，该值映射到表示为十六进制值的CommandID。|813417|然后在Groups部分中引用该组作为命令组(MyMenuGroup)的父组：|813418|<Group+guid="guidViewInBrowserPackageCmdSet"+id="MyMenuGroup"+priority="0x0000">
++<Parent+guid="aspxContextCommandSet"+id="aspxContextMenu"/>
</Group>|813419|参照为命令按钮创建的菜单组，并指向在上一步中创建的关联菜单。|813420|如果您想为多个编辑器执行此操作(即，例如ASPX、HTML和代码编辑器)您可以通过同时添加GuidSymbol和Group对每个编辑器重复此过程。您将在不同的父节点上得到同一MenuGroup点的多个Group条目，所有条目都将相应地激活。|813421|工作得很好，但是您可能必须确保使用BeforeQueryStatus事件处理程序过滤OleMenuCommand对象，以确保只有在您实际可以处理的时候才会显示菜单。|813422|entityMap^0|0|0|2|0|0|3|1Q|0|0|0|C|A|0|0|0|4|7|0|0|0|3|6|0|0|0|0|H|H|16|E|0^^$0|@$1|2|3|4|5|6|7|1G|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1H|8|@$D|1I|E|1J|F|G]]|9|@]|A|$]]|$1|H|3|-4|5|6|7|1K|8|@]|9|@]|A|$]]|$1|I|3|J|5|K|7|1L|8|@$D|1M|E|1N|F|L]]|9|@]|A|$]]|$1|M|3|N|5|K|7|1O|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|1P|8|@]|9|@]|A|$]]|$1|P|3|Q|5|6|7|1Q|8|@$D|1R|E|1S|F|L]]|9|@]|A|$]]|$1|R|3|S|5|T|7|1T|8|@]|9|@]|A|$U|V]]|$1|W|3|X|5|6|7|1U|8|@]|9|@]|A|$]]|$1|Y|3|Z|5|6|7|1V|8|@$D|1W|E|1X|F|L]]|9|@]|A|$]]|$1|10|3|11|5|T|7|1Y|8|@]|9|@]|A|$U|V]]|$1|12|3|13|5|6|7|1Z|8|@]|9|@]|A|$]]|$1|14|3|15|5|6|7|20|8|@$D|21|E|22|F|L]]|9|@]|A|$]]|$1|16|3|17|5|T|7|23|8|@]|9|@]|A|$U|V]]|$1|18|3|19|5|6|7|24|8|@]|9|@]|A|$]]|$1|1A|3|1B|5|6|7|25|8|@]|9|@]|A|$]]|$1|1C|3|1D|5|6|7|26|8|@$D|27|E|28|F|L]|$D|29|E|2A|F|L]]|9|@]|A|$]]|$1|1E|3|-4|5|6|7|2B|8|@]|9|@]|A|$]]]|1F|$]]

I was able to figure out the right command groups for the context menu. It turns out the various editors all use separate context ids and so have to be managed as separate menus so this gets messy quick.

Steps

<ol>
<li>I used the <code>HKEY_CURRENT_USER\SOFTWARE\Microsoft\VisualStudio\14.0\General</code> key and EnableVSIPLogging value of 1 to enable logging.</li>
<li>I then navigated into the editor and with the mouse on an empty area press CTRL-SHIFT and then right click the mouse</li>
</ol>

This gives the info a <code>menu group</code> like and it looks like this:

<pre><code>---------------------------
VSDebug Message
---------------------------
Menu data:
 Guid = {D7E8C5E1-BDB8-11D0-9C88-0000F8040A53}
 GuidID = 358
 CmdID = 53
 Type = 0x00000400
 Flags = 0x00000000
 NameLoc = ASPX Context
---------------------------
OK 
---------------------------
</code></pre>

The important values are the GUID and the CommandID.

Add the Guid and Command ID under <code>Symbols</code> like this to register the command set mapping the Guid to the CommandSet and the CommandId to the context menu values:

<pre class="lang-xml prettyprint-override"><code>&lt;GuidSymbol name="aspxContextCommandSet" value="{D7E8C5E1-BDB8-11D0-9C88-0000F8040A53}"&gt;
 &lt;IDSymbol name="aspxContextMenu" value="0x0035"/&gt;
&lt;/GuidSymbol&gt;
</code></pre>

Note that the value maps to the CommandID represented as a hex value.

Then reference this group as a parent for your command group (MyMenuGroup) in the <code>Groups</code> section:

<pre class="lang-xml prettyprint-override"><code>&lt;Group guid="guidViewInBrowserPackageCmdSet" id="MyMenuGroup" priority="0x0000"&gt;
 &lt;Parent guid="aspxContextCommandSet" id="aspxContextMenu"/&gt;
&lt;/Group&gt;
</code></pre>

You reference the menu group you create for you command buttons and point at the context menu created in the previous step.

If you want to do this for multiple editors (ie. the ASPX, HTML, and Code editors for example as I do) you repeat this process for each of your editors by adding both the GuidSymbol and the Group.You'll end up with multiple Group entries for the same MenuGroup point at a different parent and all will activate appropriately.

Works great, but you'll probably have to make sure you filter your <code>OleMenuCommand</code> objects with a <code>BeforeQueryStatus</code> event handler to ensure the menu shows only when you actually can handle.

blocks|key|204989|text|我需要同样的东西，我使用：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|204990|<Parent+guid="guidSHLMainMenu"+id="IDM_VS_CTXT_CODEWIN"/>|code-block|syntax|javascript|204991|所以，我只是更改了id。请参阅：https://msdn.microsoft.com/en-us/library/microsoft.visualstudio.shell.vsmenus.idm_vs_ctxt_codewin.aspx|offset|length|204992|entityMap|0|LINK|mutability|MUTABLE|url|https://msdn.microsoft.com/en-us/library/microsoft.visualstudio.shell.vsmenus.idm_vs_ctxt_codewin.aspx^0|0|0|G|2U|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|T|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|U|8|@]|9|@$I|V|J|W|1|X]]|A|$]]|$1|K|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]]|L|$M|$5|N|O|P|A|$Q|R]]]]

I needed the same thing and I used:

<pre class="lang-xml prettyprint-override"><code>&lt;Parent guid="guidSHLMainMenu" id="IDM_VS_CTXT_CODEWIN"/&gt;
</code></pre>

So, I just changed the id. See: <a href="https://msdn.microsoft.com/en-us/library/microsoft.visualstudio.shell.vsmenus.idm_vs_ctxt_codewin.aspx" rel="nofollow noreferrer">https://msdn.microsoft.com/en-us/library/microsoft.visualstudio.shell.vsmenus.idm_vs_ctxt_codewin.aspx</a>

I have an internal extension I'd like to add to Visual Studio that should hook up to the Editor Context menu - regardless of what type of file is open. I can handle enabling/visibility dynamically but essentially I'd like it to be accessible on any type of editor file.

I've not been able to find the right parent command/group ids to manage to get a custom button to display on the editor context menu. I suspect there's not a single Id but several but any guidance on what I should be looking at. Having a hard time figuring out what the proper parent command Id is to hook up to the editor context menu.

Specifically I need to be able to add View in Browser option to files that Visual Studio doesn't recognize as HTML/Web files (even though they are mapped to the appropriate editors).

Related: Is there anyway to reasonable way to discover the menu command and group names? Poking around in the SharedCommandPlace.vsct is as close as I've come but even that is proving to be very difficult to match to actual menu items.

VSIX: Adding a Menu Item to the Visual Studio Editor Context Menu

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我有一个内部扩展，我想添加到Visual Studio，它应该挂接到编辑器上下文菜单-无论什么类型的文件是打开的。我可以动态地启用/visibility，但本质上我希望它可以在任何类型的编辑器文件中访问。我找不到正确的父命令/组I来管理以在编辑器上下文菜单上显示自定义按钮。我怀疑不是一个Id，而是几个，但有任何关于我应...

问VSIX:向Visual Studio编辑器上下文菜单添加菜单项
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问VSIX:向Visual Studio编辑器上下文菜单添加菜单项EN