Visual Studio Code (VS Code) is a cross-platform script editor by Microsoft. Together with the PowerShell extension, it provides a rich and interactive script editing experience, making it easier to write reliable PowerShell scripts. Visual Studio Code with the PowerShell extension is the recommended editor for writing PowerShell scripts.
It supports the following PowerShell versions:
Before you begin, make sure PowerShell exists on your system. For modern workloads on Windows, macOS, and Linux, see the following links:
For traditional Windows PowerShell workloads, see Installing Windows PowerShell.
Important
The Windows PowerShell ISE is still available for Windows. However, it's no longer in active feature development. The ISE only works with PowerShell 5.1 and older. As a component of Windows, it continues to be officially supported for security and high-priority servicing fixes. we've no plans to remove the ISE from Windows.
Install VS Code and the PowerShell ExtensionInstall Visual Studio Code. For more information, see the overview Setting up Visual Studio Code.
There are installation instructions for each platform:
Install the PowerShell Extension.
code in a console or code-insiders if you installed Visual Studio Code Insiders.ext install powershell and press Enter.For example, to create a new file, click File > New. To save it, click File > Save and then provide a filename, such as HelloWorld.ps1. To close the file, click the X next to the filename. To exit VS Code, File > Exit.
Some systems are set up to require validation of all code signatures. You may receive the following error:
Language server startup failed.
This problem can occur when PowerShell's execution policy is set by Windows Group Policy. To manually approve PowerShell Editor Services and the PowerShell extension for VS Code, open a PowerShell prompt and run the following command:
Import-Module $HOME\.vscode\extensions\ms-vscode.powershell*\modules\PowerShellEditorServices\PowerShellEditorServices.psd1
You're prompted with Do you want to run software from this untrusted publisher? Type A to run the file. Then, open VS Code and verify that the PowerShell extension is functioning properly. If you still have problems getting started, let us know in a GitHub issue.
With PowerShell installing side-by-side with Windows PowerShell, it's now possible to use a specific version of PowerShell with the PowerShell extension. This feature looks at a few well-known paths on different operating systems to discover installations of PowerShell.
Use the following steps to choose the version:
If you installed PowerShell to a non-typical location, it might not show up initially in the Session Menu. You can extend the session menu by adding your own custom paths as described below.
The PowerShell session menu can also be accessed from the {} icon in the bottom right corner of status bar. Hovering on or selecting this icon displays a shortcut to the session menu and a small pin icon. If you select the pin icon, the version number is added to the status bar. The version number is a shortcut to the session menu requiring fewer clicks.
Note
Pinning the version number replicates the behavior of the extension in versions of VS Code before 1.65. The 1.65 release of VS Code changed the APIs the PowerShell extension uses and standardized the status bar for language extensions.
Configuration settings for Visual Studio CodeFirst, if you're not familiar with how to change settings in VS Code, we recommend reading Visual Studio Code's settings documentation.
After reading the documentation, you can add configuration settings in settings.json.
{
"editor.renderWhitespace": "all",
"editor.renderControlCharacters": true,
"files.trimTrailingWhitespace": true,
"files.encoding": "utf8bom",
"files.autoGuessEncoding": true
}
If you don't want these settings to affect all files types, VS Code also allows per-language configurations. Create a language-specific setting by putting settings in a [<language-name>] field. For example:
{
"[powershell]": {
"files.encoding": "utf8bom",
"files.autoGuessEncoding": true
}
}
You can add other PowerShell executable paths to the session menu through the Visual Studio Code setting: powershell.powerShellAdditionalExePaths.
You can do this using the GUI:
You can add as many additional paths as you like. The added items show up in the session menu with the given key as the name.
Alternatively you can add key-value pairs to the object powershell.powerShellAdditionalExePaths in your settings.json:
{
"powershell.powerShellAdditionalExePaths": {
"Downloaded PowerShell": "C:/Users/username/Downloads/PowerShell/pwsh.exe",
"Built PowerShell": "C:/Users/username/src/PowerShell/src/powershell-win-core/bin/Debug/net6.0/win7-x64/publish/pwsh.exe"
},
}
Note
Prior to version 2022.5.0 of the extension, this setting was a list of objects with the required keys exePath and versionName. A breaking change was introduced to support configuration via GUI. If you had previously configured this setting, please convert it the new format. The value given for versionName is now the Key, and the value given for exePath is now the Value. You can do this more easily by resetting the value and using the Settings interface.
To set the default PowerShell version, set the value powershell.powerShellDefaultVersion to the text displayed in the session menu (the text used for the key):
{
"powershell.powerShellAdditionalExePaths": {
"Downloaded PowerShell": "C:/Users/username/Downloads/PowerShell/pwsh.exe",
},
"powershell.powerShellDefaultVersion": "Downloaded PowerShell",
}
After you've configured this setting, restart VS Code or to reload the current VS Code window from the Command Palette, type Developer: Reload Window.
If you open the session menu, you now see your additional PowerShell installations.
Tip
If you build PowerShell from source, this is a great way to test out your local build of PowerShell.
Debugging with Visual Studio Code No-workspace debuggingIn VS Code version 1.9 (or higher), you can debug PowerShell scripts without opening the folder that contains the PowerShell script.
You should see the Debug actions pane appear that allows you to break into the debugger, step, resume, and stop debugging.
Workspace debuggingWorkspace debugging refers to debugging in the context of a folder that you've opened from the File menu using Open Folder.... The folder you open is typically your PowerShell project folder or the root of your Git repository. Workspace debugging allows you to define multiple debug configurations other than just debugging the currently open file.
Follow these steps to create a debug configuration file:
Open the Debug view on Windows or Linux by pressing Ctrl+Shift+D. On macOS, press Cmd+Shift+D.
Click the create a launch.json file link.
From the Select Environment prompt, choose PowerShell.
Choose the type of debugging you'd like to use:
VS Code creates a directory and a file .vscode\launch.json in the root of your workspace folder to store the debug configuration. If your files are in a Git repository, you typically want to commit the launch.json file. The contents of the launch.json file are:
{
"version": "0.2.0",
"configurations": [
{
"type": "PowerShell",
"request": "launch",
"name": "PowerShell Launch (current file)",
"script": "${file}",
"args": [],
"cwd": "${file}"
},
{
"type": "PowerShell",
"request": "attach",
"name": "PowerShell Attach to Host Process",
"processId": "${command.PickPSHostProcess}",
"runspaceId": 1
},
{
"type": "PowerShell",
"request": "launch",
"name": "PowerShell Interactive Session",
"cwd": "${workspaceRoot}"
}
]
}
This file represents the common debug scenarios. When you open this file in the editor, you see an Add Configuration... button. You can click this button to add more PowerShell debug configurations. One useful configuration to add is PowerShell: Launch Script. With this configuration, you can specify a file containing optional arguments that are used whenever you press F5 no matter which file is active in the editor.
After the debug configuration is established, you can select the configuration you want to use during a debug session. Select a configuration from the debug configuration drop-down in the Debug view's toolbar.
Troubleshooting the PowerShell extensionIf you experience any issues using VS Code for PowerShell script development, see the troubleshooting guide on GitHub.
Useful resourcesThere are a few videos and blog posts that may be helpful to get you started using the PowerShell extension for VS Code:
VideosThe PowerShell extension's source code can be found on GitHub.
If you're interested in contributing, Pull Requests are greatly appreciated. Follow along with the developer documentation on GitHub to get started.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4