FAQ

Here are answers to some of the common asked questions about the PowerShell extension for Visual Studio Code:

Q. The syntax colorization of parts of my PowerShell do not seem correct. Where do I file an issue about this?
A. The syntax colorization for PowerShell is provided by the EditorSyntax project on GitHub. Please file issues related to syntax colorization on that project.

Q. I see incorrect code style warnings/problems. Where to report them?
A. If the warning message starts with [PSScriptAnalyzer], then please report it in the PSScriptAnalyzer repo here.

Q. What is wrong with code folding in my PowerShell scripts?
A. The code folding feature is provided by Visual Studio Code and not the PowerShell extension. Code folding in VSCode is based purely on indentation levels. This causes issues with PowerShell here strings which have to be terminated in column 0. There is an issue on the VSCode GitHub site tracking this.

Q. How come PSReadline features like history recall don't work in the PowerShell Integrated Console.
A. Integration of PSReadline into the PowerShell Integrated Console is currently being worked on.

Q. How do I debug my PowerShell script
A. This topic is best covered in the following two Scripting Guys blog posts: Debugging PowerShell script in Visual Studio Code – Part 1 and Part 2

Q. How to enable Verbose Logging ?
A. To enable verbose logging open user settings (To open user settings, open the command palette and type user settings). Once your settings are open, search for powershell.developer.editorServicesLogLevel setting and set it to verbose.