This post was originally published on this site

We are excited to announce that an update to the PowerShell Extension for Visual Studio Code is now available in the extension marketplace.

In recent updates, we include a new “attach .NET debugger” debug configuration for binary PowerShell modules, better handling of start-up failures when the PowerShell version is unsupported, and have merged the PowerShell Preview extension and PowerShell “stable” extension into a single extension with a Prelease release channel.

The “PowerShell Preview” extension has now been officially deprecated, with “preview” releases now available via the “pre-release” option on the stable “PowerShell” extension in the marketplace. While you should be migrated automatically, feel free to just uninstall the preview and install the now one-and-only extension, but please keep testing our pre-releases! This change makes it much simpler to use, as you no longer have to switch between two different extensions and instead can use VS Code’s marketplace to install your choice of version!

Highlights in the March, April and May Releases

Note that these updates all shipped in our prelease channel for VS Code before shipping in our stable channel.

• vscode-powershell #4543 – Update startup logic to handle session failure reasons.
• vscode-powershell #4521 – Handle end-of-support PowerShell with error message.
• vscode-powershell #4517 – Fix attachDotnetDebugger with custom config. (Thanks @fflaten!)
•   vscode-powershell #4511 – Add additional debug configuration templates for Pester and binary modules. (Thanks @JustinGrote!)
•   vscode-powershell #4510 – Improve extension authoring experience with new Build Tasks and Launch Configs. (Thanks @JustinGrote!)
• vscode-powershell #4502 – Enable VS Code unit tests in Linux CI.
• PowerShellEditorServices #2016 – Add guide to configure Neovim. (Thanks @csc027!)
• vscode-powershell #3716 – Adopt the pre-release extension feature.
• vscode-powershell #4453 – Fix GenerateBugReport command to pre-fill template.
• vscode-powershell #3604 – Add document symbols for #region.
• vscode-powershell #3192 – Fix New-EditorFile adding content in current file. (Thanks @fflaten!)

For the full list of changes please refer to our changelog.

Getting Support and Giving Feedback

While we hope the new implementation provides a much better user experience, there are bound to be issues. Please let us know if you run into anything.

If you encounter any issues with the PowerShell Extension in Visual Studio Code or have feature requests, the best place to get support is through our GitHub repository.

Sydney Smith
PowerShell Team

The post PowerShell Extension for Visual Studio Code Spring 2023 Update appeared first on PowerShell Team.