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
IMPORTANT: I'm filing this more broadly on Visual Studio Code, at the request of @daviwil, after initially filing it on the PowerShell extension for VSCode.
When you open VSCode and run a PowerShell script, for the first time in the new session, the PowerShell Extension switches VSCode from the Explorer context, into the Debugging context. Subsequent executions do not do this.
Reproduction Steps
Open VSCode
Open a project with a PowerShell script (in my case, a Pester test script)
Hit F5 to run the script
NOTICE: VSCode changes into debugging context, and script runs/exits
Go back to Explorer context in VSCode (CTRL + SHIFT + E)
Hit F5 to run the script again
NOTICE: VSCode doesn't change into the debugger context
What does change into the debugger context mean?
If you mean opens debug console then this is as designed as you can configure the internalConsoleOptions in your launch.json.
More details can be found here #4045
If that is not the case, please let me know and I will reopen this issue - thanks!
@isidorn It opens the Debugger pane on the Sidebar, which isn't necessarily desirable. Also, the behavior is inconsistent, because it does it the first time, but doesn't do it after that.
IMPORTANT: I'm filing this more broadly on Visual Studio Code, at the request of @daviwil, after initially filing it on the PowerShell extension for VSCode.
System Details
$PSVersionTable
:Issue Description
When you open VSCode and run a PowerShell script, for the first time in the new session, the PowerShell Extension switches VSCode from the Explorer context, into the Debugging context. Subsequent executions do not do this.
Reproduction Steps
Originally filed here: PowerShell/vscode-powershell#283
Cheers,
Trevor Sullivan
Docker Captain
Microsoft MVP: Cloud & Data Center Management
https://trevorsullivan.net
https://twitter.com/pcgeek86
The text was updated successfully, but these errors were encountered: