You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Last stable vscode, we introduced a "feature" that would prompt you to save an untitled file before debugging it. This is because most debug adapters don't support debugging untitled files... But PowerShell does!
A setting was added in insiders to control this behavior now so Untitled PowerShell files are now debuggable again.
At a minimum, I think this setting should be added to ISE Mode. Users will expect F5 to run their script, even if it's not saved on disk, and ISE Mode was made for the beginner in mind.
Additionally, consider adding the following setting to the user's setting on start up/install:
Summary of the new feature
Last stable vscode, we introduced a "feature" that would prompt you to save an untitled file before debugging it. This is because most debug adapters don't support debugging untitled files... But PowerShell does!
A setting was added in insiders to control this behavior now so Untitled PowerShell files are now debuggable again.
More info: microsoft/vscode#114890
Proposed technical implementation details (optional)
At a minimum, I think this setting should be added to ISE Mode. Users will expect F5 to run their script, even if it's not saved on disk, and ISE Mode was made for the beginner in mind.
Additionally, consider adding the following setting to the user's setting on start up/install:
Which will only apply this setting to PowerShell files.
The text was updated successfully, but these errors were encountered: