Move Remote Debugger Launcher menu to Debug menu

[Copilot]

Relocates the "Remote Debugger Launcher" submenu from Tools to Debug in Visual Studio's top-level menu bar.

Changes

• Modified RemoteDebuggerLauncherPackage.vsct:
  • Changed parent menu from IDM_VS_MENU_TOOLS to IDM_VS_MENU_DEBUG in the groupidToolsItem Group definition

<Group guid="guidRemoteDebuggerLauncherPackageCmdSet" id="groupidToolsItem" priority="0x0600">
  <Parent guid="guidSHLMainMenu" id="IDM_VS_MENU_DEBUG" />
</Group>

All extension commands (Deploy remote target, Clean remote target, Install debugger/runtime, Setup SSH/HTTPS) now appear under Debug where debugging tools belong.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• 1n8vsblobprodwus2184.vsblob.vsassets.io
  • Triggering command: /usr/bin/dotnet dotnet restore RemoteDebuggerLauncherExtension.sln (dns block)
• 84hvsblobprodwus2148.vsblob.vsassets.io
  • Triggering command: /usr/bin/dotnet dotnet restore RemoteDebuggerLauncherExtension.sln (dns block)
• izzvsblobprodwus2142.vsblob.vsassets.io
  • Triggering command: /usr/bin/dotnet dotnet restore RemoteDebuggerLauncherExtension.sln (dns block)
• k4pvsblobprodwus2140.vsblob.vsassets.io
  • Triggering command: /usr/bin/dotnet dotnet restore RemoteDebuggerLauncherExtension.sln (dns block)
• kafvsblobprodwus2165.vsblob.vsassets.io
  • Triggering command: /usr/bin/dotnet dotnet restore RemoteDebuggerLauncherExtension.sln (dns block)
• vd2vsblobprodwus2150.vsblob.vsassets.io
  • Triggering command: /usr/bin/dotnet dotnet restore RemoteDebuggerLauncherExtension.sln (dns block)
• y5lvsblobprodwus2179.vsblob.vsassets.io
  • Triggering command: /usr/bin/dotnet dotnet restore RemoteDebuggerLauncherExtension.sln (dns block)
• zugvsblobprodwus2169.vsblob.vsassets.io
  • Triggering command: /usr/bin/dotnet dotnet restore RemoteDebuggerLauncherExtension.sln (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Move the extension's menu items to the "Debug" top-level menu</issue_title>
<issue_description>
That's where they belong...</issue_description>

<agent_instructions>Move the existing "Remote Debugger Launcher" Menu Item appearing in the Extensions menu to appear in the Visual Studio Debug.

• Modify the existing Command Group guidRemoteDebuggerLauncherPackageCmdSet, change the parent to guidSHLMainMenu</agent_instructions>

Comments on the Issue (you are @copilot in this section)

@MichaelKoster70 @copilot We need to move the exiting "Remote Debugger Launcher" menu item to appear under to the Visual Studio Debug menu in our VSIX extension.

Please:

• Identify the .vsct file location.
• Find the AsyncPackage class where commands are registered.
• Locate the folder for command classes.
  Then propose a plan and list the files you will modify.</comment_new>

• Fixes Move the extension's menu items to the "Debug" top-level menu #81

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[softworkz]

I think it's important for the menu to be wrapped by divider items to make it clear that this is a special group of features. But since that is already happening in the Tools menu, it will probably be the same like there anyway.