Top vscode-powershell issues

New temporary console debugging should probably not close until user presses key

Area-Debugging Area-Integrated Console Issue-Enhancement
rkeithhill picture rkeithhill·22 Jun 2017·8 Comments
👍9 ❤4

PowerShell extension uses PSScriptAnalyzer settings file - Cannot update rules

Area-Configuration Issue-Bug
PowerDBAKlaas picture PowerDBAKlaas·20 Jun 2017·9 Comments
👀1

Killing the PSIC generates an error

Area-Integrated Console Issue-Bug
rkeithhill picture rkeithhill·5 Jun 2017·3 Comments
👍2

Auto set breakpoints

Area-Debugging Issue-Enhancement
dfinke picture dfinke·1 May 2017·4 Comments
👍1

"throw" not offered as keyword in autocompletion

Area-IntelliSense Issue-Bug
carlocardella picture carlocardella·29 Apr 2017·9 Comments
👍2

EditorServices.log logfile takes extremely large amount of disk size [macOS]

Area-Logging Issue-Bug
peterblazejewicz picture peterblazejewicz·13 Apr 2017·4 Comments

F8: New-PSSession requires selecting terminal windows and hit enter to show result

Area-Integrated Console Issue-Bug Needs-Repro-Info verify-fix
bgelens picture bgelens·10 Apr 2017·3 Comments

Calling Set-PSBreakpoint in console doesn't cause breakpoint icon to appear in file

Area-Debugging Issue-Bug
daviwil picture daviwil·7 Apr 2017·14 Comments

F5 on Untitled-1 file in 0.12.1 with existing .vscode\launch.json from prev version hangs debugger

Area-Debugging Issue-Bug
daviwil picture daviwil·5 Apr 2017·4 Comments

Prompt written on Linux or macOS has black background

Area-Integrated Console Issue-Bug
daviwil picture daviwil·31 Mar 2017·3 Comments
 Previous issues
Next issues