
Install the Visual Studio Code PowerShell extension via EXE installer The steps we are covering should be the same or similar for other versions. Install Visual Studio Code v1.4.2 on Windows 10. Perform some minor tweaks to the PowerShell console Install the PowerShell v6.2.4 package from GitHub manually via MSI on Windows 10. In this tutorial, you're going to install both PowerShell and Visual Studio Code. Local administrator permissions - You'll need to be logged in with local administrator permissions or equivalent to install software. The demo environment will use Windows 10 build 1903. Windows 10 - Any build of Windows 10 released in 2019 or 2020 will work. To ensure your environment is as close to the demo environment as possible, please be sure you meet the following prerequisites before starting. Visual Studio Code is the new focus and all new development is focused on it as Microsoft's preferred editor.īy the time you've completed the walkthrough in this post, you'll have PowerShell and Visual Studio Code installed with some basic configuration to hit the ground running. Even though the PowerShell ISE works find for newcomers, you shouldn't get used to it. Note that you will not learn how to use the PowerShell ISE in this tutorial series. To take care of all of the set up as early as possible, we're going to knock out both of these tasks in this post.

One of the most popular PowerShell editors is Visual Studio Code. Since I'm assuming you're going to actually create some scripts at some point, you'll also need a great code editor.

Unlike Windows PowerShell, which comes pre-installed with Windows, plain ol' PowerShell formerly known as PowerShell Core must be installed separately. In this tutorial series, you're going to learn with PowerShell (not Windows PowerShell). To start writing some awesome PowerShell scripts, you must have it installed. Windows PowerShell, PowerShell Core and PowerShell: Huh? If you'd like to catch up (or skip ahead - more posts coming soon), click on the appropriate post below. *If you're just joining us, this post is part of a 12-part series on Getting Started with PowerShell.
