vscode-powershell: Temporary Console does not allow interactive debugging via console
System Details
-
Operating system name and version: Windows 10 Enterprise x64 1709
-
VS Code version: Version 1.22.0-insider Commit 5450fdc79778b5a76a27ea7e5fd68e9ebbe44107 Date 2018-03-12T05:15:51.483Z Shell 1.7.9 Renderer 58.0.3029.110 Node 7.9.0 Architecture x64
-
PowerShell extension version: 1.6.0
-
Output from
$PSVersionTable: PSVersion 6.0.0-beta.9 PSEdition Core GitCommitId v6.0.0-beta.9 OS Microsoft Windows 10.0.16299 Platform Win32NT PSCompatibleVersions {1.0, 2.0, 3.0, 4.0…} PSRemotingProtocolVersion 2.3 SerializationVersion 1.1.0.1 WSManStackVersion 3.0
Issue Description
When using the Temporary Console launch configuration, “Powershell Launch Current File in Temporary Console” when a breakpoint is hit and you attempt to use the integrated console, the debugging console only accepts one input, does not actually do anything with the input and prevents further input into the console.
To reproduce:
- Change your configuration to, “Powershell Launch Current File in Temporary Console”
- Launch a script with a breakpoint
- Wait to hit the breakpoint and try to do something in the integrated console
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Reactions: 3
- Comments: 17 (6 by maintainers)
I can no longer reproduce this! Thanks!
Yep that was me! If I don’t get lazy I’ve got a couple more to file tomorrow 😃
Did we meet at PSHSummit? Someone mentioned this to me yesterday 😃
This sounds like a bug for sure.