attempting to enter debugger from commandline gives error in extension version 2025.0.0 #5175
Open
6 tasks done
Labels
Area-Debugging
Issue-Bug
A bug to squash.
Verified
This issue has been determined to be a legitimate issue that requires a fix.
Prerequisites
Summary
Starting with Powershell extension version 2025.0.0, whenever I do something at the terminal command prompt that tries to engage the debugger, a screen opens up with this error message, "The editor could not be opened due to an unexpected error. Please consult the log for more details."
I found logs at ...AppData\Roaming\Code\User\globalStorage\ms-vscode.powershell\logs , but the files under the random GUID type folder there haven't been written to since February; so, I don't know what that means or if there are logs elsewhere.
Usually, I can open another file, paste my command in there and hit F5 and that works. But, sometimes even then I get the error message. And, that's pretty clumsy. In previous versions of the extension, I was able to put wait-debugger; in front of my command when I wanted to make it go into the debugger. But, if I just run a command like
Get-Process -Name bogus -ErrorAction Break
I also get the error.This has happened with 3 different machines and it's pretty consistent.
Does anyone use something other than VS Code with the Powershell extension to debug Powershell scripts? What's the most popular way to do this?
PowerShell Version
Visual Studio Code Version
Extension Version
ms-vscode.?[7mpowershell?[[email protected]
Steps to Reproduce
run a command in the terminal that tries to open the debugger
Visuals
No response
Logs
No response
The text was updated successfully, but these errors were encountered: