One advantage of this approach is that a crash of the PowerShell Editor Services process doesn’t cause Visual Studio Code to crash. PowerShell Editor Services runs in a separate process and supplies both language and debugging services to Visual Studio Code via a JSON remote procedure call (RPC) protocol that’s defined by Visual Studio Code. These features are provided by the PowerShell extension, or, more accurately, by the PowerShell Editor Services module which comes with the PowerShell extension.

In the first of this two-part series, we will cover the many features of the PowerShell debugger for Visual Studio Code. If you don’t already have Visual Studio Code configured with the PowerShell extension, read those blog posts to get caught up. In previous blog posts, we covered how to get started with PowerShell development in Visual Studio Code and the editing features of Visual Studio Code and the PowerShell extension. Summary: Here’s a look at the many features of the PowerShell debugger for Visual Studio Code.

Visual studio code debug bash script