Cannot Set Breakpoints When Remote Debugging PowerShell

[prpercival]

Prerequisites

• [X] I have written a descriptive issue title.
• [X] I have searched all open and closed issues to ensure it has not already been reported.
• [X] I have read the troubleshooting guide.
• [X] I am sure this issue is with the extension itself and does not reproduce in a standalone PowerShell instance.
• [X] I have verified that I am using the latest version of Visual Studio Code and the PowerShell extension.
• [X] If this is a security issue, I have read the security issue reporting guidance.

Summary

I am attempting to use VSCode for remote editing and debugging PowerShell files following this guide. I am able to run and attempt to debug my remote file after opening with psedit <filename>, but it appears breakpoints do not work as expected. It appears VSCode opens a file on my host machine with the path of the remote file (which does not exist on the host) and tries to attach the debugger to that. It will respect the original breakpoint set before it ran initially and I can even see variables on the left side, but I do not have the ability to alter breakpoints on the file or inspect variable values by hovering over them.

PowerShell Version

Major  Minor  Build  Revision
-----  -----  -----  --------
5      1      22621  963

Visual Studio Code Version

1.77.3
704ed70d4fd1c6bd6342c436f1ede30d1cff4710
x64

Extension Version

[email protected]

Steps to Reproduce

• Open VSCode, create a new file, set file type to PowerShell
• Wait for integrated console to come up, type in the following:

Enter-PSSession -ComputerName <IPAdress> -Credential $credObject
New-Item test.ps1
psedit test.ps1

• Paste or write whatever code you want to execute and then CTRL + S
• Set a breakpoint after our variable assignment and hit F5 to debug. This will attempt to open a file on the host with the path of the remote file. This file does not exist. It will also remove the breakpoint from the original remote file and put it on this file.
• We can now no longer create new breakpoints or hover over values.

Visuals

Logs

Logs.zip

[SydneyhSmith]

Thanks @prpercival for opening this issue, sorry to hear that you are hitting a bug, in the next month or so we have a big PR coming in to make some fixes to debugging that may or may not fix this issue, we will let you know when that is in and you can test it out...in the meantime feel free to try and see if this repros in PowerShell 7

[prpercival]

I appreciate the response and look forward to testing out the fixes!

[kornflex]

Same problem for me :/

[elmidwill]

Was there ever a solution for this.

[prpercival]

I believe this issue does not occur in v2023.6.0 (current is v2023.8.0). You could try downgrading the extension and see if that works for you.

[rosskouk]

This issue still exists in v2024.2.2, are there any plans to fix the issue? This feature would be a big selling point in trying to migrate users from ISE.

Downgrading to version v2023.6.0 does result in some of the variable data being available, but it isn't usable as the file disappears from the screen when a breakpoint is reached.