🐛 📺 vscode-powershell #4453 – Fix GenerateBugReport command to pre-fill template.(Thanks ✨ 👷 vscode-powershell #3716 – Adopt the pre-release extension feature. ✨ 📖 PowerShellEditorServices #2016 – Add guide to configure Neovim.(Thanks ✨ 👷 vscode-powershell #4502 – Enable VS Code unit tests in Linux CI.

(Thanks 🔍🙏 vscode-powershell #4510 – Improve extension authoring experience with new Build Tasks and Launch Configs. (Thanks 🔍 vscode-powershell #4511 – Add additional debug configuration templates for Pester and binary modules.

🐛 🔍 vscode-powershell #4517 – Fix attachDotnetDebugger with custom config.

🐛 🙏 vscode-powershell #4521 – Handle end-of-support PowerShell with error message.

🐛 🛫 vscode-powershell #4543 – Update startup logic to handle session failure reasons.

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

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 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.

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. In recent updates, we include a new “attach. We are excited to announce that an update to the PowerShell Extension for Visual Studio Code is now available in the extension marketplace.

Visual studio 2012 update