Attaching to WSL process from a visual studio extension.

To attach to WSL processes programmatically, you can approach this task by leveraging the existing functionality in Visual Studio. Here's a general guideline based on what you shared:

1. Access the Debugger: You’ll want to work with the IVsDebugger interface, which provides methods to start debugging sessions.
2. Configure the Connection Type: You need to specify Windows Subsystem for Linux (WSL) as the connection type. This is crucial because it directs the debugger to work with WSL.
3. Attach to the Process: While LaunchDebugTargets4 is typically used for launching new debugging sessions, you will likely want to look into methods similar to AttachToProcess, making sure you can specify the WSL distribution you need to attach to.
4. Set up the Configuration: Create a debug launch configuration that matches how you set it up in the Visual Studio UI. This includes specifying any necessary parameters for processes running inside the WSL environment. The exact details may depend on the SDK version and the specifics of the process you're debugging.

Yes, use IVsDebugger4.LaunchDebugTargets4(), and set it up like this:

dlo = DLO_Attach

bstrExe = "<your PID or exe>"

bstrPortName = "SSH:wsl+<DistroName>" (e.g., SSH:wsl+Ubuntu)

guidLaunchDebugEngine = appropriate engine CLSID (C++, .NET Core, etc.)

That bstrPortName is the key for WSL. Let me know if you need help with engine GUIDs or getting the distro name!

Hope you're doing well , we're following up on the ticket. Please let us know issue persist are resolved.

To attach to a WSL process in a VSIX extension, don't use LaunchDebugTargets4 directly. Instead, use VsDebugTargetInfo2 and the above error means one of those values are missing or wrong.

Thank you for reaching out. Please find the answer below.

You're absolutely right that VsDebugTargetInfo2 is an older API and not ideal for modern managed code scenarios.
It also doesn't map directly to LaunchDebugTargets4, and in many cases, LaunchDebugTargets2 is a more appropriate choice.

To attach to a WSL process from a VSIX extension, the recommended approach is to use IVsDebugger4.LaunchDebugTargets4() with a properly configured VsDebugTargetInfo4 structure.

Here's how you can set it up for WSL:

VsDebugTargetInfo4[] targets = new VsDebugTargetInfo4[1];

targets[0].cbSize = (uint)Marshal.SizeOf(typeof(VsDebugTargetInfo4));

targets[0].dlo = (uint)DEBUG_LAUNCH_OPERATION.DLO_AlreadyRunning;

targets[0].bstrExe = "<your-exe-or-pid>"; // e.g., "464" or "myapp"

targets[0].bstrPortName = "SSH:wsl+<DistroName>"; // e.g., "SSH:wsl+Ubuntu"

targets[0].guidLaunchDebugEngine = /* appropriate engine GUID, e.g., NativeOnly_guid */;

targets[0].dwProcessId = <your-process-id>; // optional

targets[0].bstrRemoteMachine = null;

IVsDebugger4 debugger = (IVsDebugger4)Package.GetGlobalService(typeof(SVsShellDebugger));

int hr = debugger.LaunchDebugTargets4(1, targets);

The key part for WSL is setting bstrPortName to "SSH:wsl+<DistroName>", which tells Visual Studio to connect to the WSL environment.

If issue still persist after following all the steps, we’ll be happy to assist further if needed.