Top vscode-powershell issues

Add option to launch and debug external powershell.exe

Area-Debugging Issue-Enhancement
clmcgrath picture clmcgrath·7 Feb 2017·7 Comments
👍2 👀1

"Go to Definition" should follow Import-Module references

Area-Symbols & References Issue-Enhancement
176coding picture 176coding·3 Jan 2017·5 Comments
👍12 ❤1

Add an option to load PowerShell profiles in debug sessions

Area-Configuration Issue-Enhancement
LethiferousMoose picture LethiferousMoose·22 Dec 2016·11 Comments

Add "Apply All Suggested Fixes" command to apply all PSScriptAnalyzer fixes

Issue-Enhancement
dfinke picture dfinke·19 Dec 2016·8 Comments
👍5

Provide commonly used ISE hotkey compatibility

ISE-Compatibility Issue-Enhancement
daviwil picture daviwil·12 Oct 2016·2 Comments
👍3 😄1

VS Code "powershell.developer.powerShellExePath" not changing path to executable

MaximoTrinidad picture MaximoTrinidad·17 Sep 2016·9 Comments

Debugger cannot find [System.Drawing.Color] when in script

gerane picture gerane·7 Jul 2016·7 Comments

Expand aliases works silently, needs 'running indicator'

Area-UI Hackathon Issue-Enhancement Up-for-Grabs
vors picture vors·10 Jun 2016·8 Comments

Extra Intellisense coming back for argument completers

Area-IntelliSense Issue-Bug Resolution-External
pcgeek86 picture pcgeek86·28 Apr 2016·20 Comments
👍1

Wildcard commands aren't auto-completing

Area-IntelliSense Issue-Bug
pcgeek86 picture pcgeek86·21 Apr 2016·10 Comments
👀1
 Previous issues
Next issues