The most significant change is the update to OmniSharp v0.19.2, from the previous version v0.18.3, released in November 2020. The intention of this change is to increase predictability, as double-clicking PowerShell variables now selects the same portion that the extension highlights (with the exception of scoped variables due to the continued inclusion of : as a word separator).įor the full list of updates please refer to the changelog. Since we have disabled semantic highlighting by default now, if you wish to re-enable it, use: Fix unintentional module import triggered by completions (Thanks vscode-powershell #715.Fix duplicated command registrations (Thanks vscode-powershell #3320.
Upgrade OmniSharp to v0.19.2 PowerShellEditorServices #1491.Stop prompting to save untitled PowerShell files when debugging vscode-powershell #3338.Exclude - and $ from PowerShell wordSeparators vscode-powershell #3359.Disable semantic highlighting by default vscode-powershell #3221.This incremental release incorporates a major update to OmniSharp, the Language Server Protocol library we use (like many other VSCode extensions). Behind the scenes there has also been a concerted effort to improve our build and release processes, with the intention of accelerating our release cadence. What’s new in the PowerShell Extension release This blog will explain what is new in this release as well as what you can expect from the extension in the coming months. We are excited to announce that an update to our PowerShell extension is now available on the Visual Studio Code Marketplace.