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
When launching the current powershell file editor tab with F5 or Ctrl+F5 with a launch setting that includes createTemporaryIntegratedConsole : true, then in the preview extension the terminal tab [TEMP] Powershell Extension will be (re-)created, but it will not be switched to. Instead the persistent terminal tab Powershell Extension is shown.
This behavior is erroneous and super irritating, as you may think the script wasn't started at all.
In the released powershell extension the '[TEMP]Powershell Extension' tab is shown instead
PowerShell Version
(Powershell Version does not matter, same error with winps 5.1)Name Value---- -----PSVersion 7.2.1PSEdition CoreGitCommitId 7.2.1OS Microsoft Windows 10.0.14393Platform Win32NTPSCompatibleVersions {1.0, 2.0, 3.0, 4.0…}PSRemotingProtocolVersion 2.3SerializationVersion 1.1.0.1WSManStackVersion 3.0
Hi @Hetshu! I think we just got this fixed in the PowerShell Preview for VS Code. Could you verify if this issue still reproduces using the preview extension?
Prerequisites
Summary
When launching the current powershell file editor tab with F5 or Ctrl+F5 with a launch setting that includes
createTemporaryIntegratedConsole : true
, then in the preview extension the terminal tab[TEMP] Powershell Extension
will be (re-)created, but it will not be switched to. Instead the persistent terminal tabPowershell Extension
is shown.This behavior is erroneous and super irritating, as you may think the script wasn't started at all.
In the released powershell extension the '[TEMP]Powershell Extension' tab is shown instead
PowerShell Version
Visual Studio Code Version
Extension Version
Steps to Reproduce
Start a powershell script with F5 or Ctrl+F5
with this launch config
Watch what Terminal tab is active.
The [TEMP] Powershell Extension tab should be active in the terminan pane, but it is not.
Visuals
No response
Logs
No response
The text was updated successfully, but these errors were encountered: