PowerShell Remoting uses the Windows Remote Management (WinRM) protocol, which is enabled by default in Windows Server 2012 and later versions. That shouldn’t be an issue with any modern version of Windows. Both the PC on which VS Code is installed and the remote Windows device must be running Windows PowerShell.

There are a couple of prerequisites that you need to meet before you can use remoting. Connect to a Remote Device Inside Visual Studio Code But what if you could run the code on the remote device without leaving VS Code? With some help from PowerShell Remoting, you can do just that. VS Code is certainly not perfect, but Microsoft has stopped developing the PowerShell ISE so if you want the latest experience, VS Code is the way to go.īut what if you are developing code that needs to be tested on a remote device? You could manually copy any code changes to the remote device each time you need to run a test but that is time consuming and a pain because you end up with two copies of the file, one locally and another on the remote device. When you are working on PowerShell scripts, it’s standard practice to use the Windows PowerShell Integrated Scripting Environment (ISE) or other code editor, like the popular Visual Studio (VS) Code from Microsoft.

Run code in visual studio