Open prpercival opened 1 year ago
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
I appreciate the response and look forward to testing out the fixes!
Same problem for me :/
Was there ever a solution for this.
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.
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.
Prerequisites
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
Visual Studio Code Version
Extension Version
Steps to Reproduce
CTRL + S
Visuals
Logs
Logs.zip