Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Switch branches/tags

Name already in use

A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?
Go to file
Cannot retrieve contributors at this time

PowerShell Preview Extension Release History March 2020

This document shows the combined changes that were moved from the Preview extension to the stable extension as part of the March 2020 release.

Top Features


Thursday, February 20, 2020


  • 🐛📖 vscode-PowerShell #2470 - Fix incorrect reference to New-ManifestModule in documentation. (Thanks @rbleattler!)
  • 🐛📺 vscode-PowerShell #2469 - Close other open pwsh instances when updating PowerShell.
  • 🐛📟 vscode-PowerShell #2434 - Use a new VSCode API to hide the integrated terminal from the shell list until debugging when showOnStartup is disabled.
  • 🐢 vscode-PowerShell #2445 - Add Run/Debug Pester tests context menu options in the VSCode explorer for Pester test files. (Thanks @bergmeister!)
  • 🐛🐢 vscode-PowerShell #2438 - Fixes test failures in Pester contexts not showing up in the Problems pane. (Thanks @tillig!)
  • 🐛🔍 vscode-PowerShell #2548 - Show error message instead of hanging when temp debugging is used with an untitled file.
  • 👷 vscode-PowerShell #2465 - Move macOS CI images to 10.14 (Thanks @bergmeister!)


  • 🐛📁 vscode-PowerShell #2421 - Fix WorkspacePath so that references work with non-ASCII characters.
  • 🐛📟 vscode-PowerShell #2372 - Fix prompt behavior when debugging.
  • 🐛🛫 PowerShellEditorServices #1171 - Fix race condition where running multiple profiles caused errors.
  • 🐛📟 vscode-PowerShell #2420 - Fix an issue where pasting to a Get-Credential prompt in some Windows versions caused a crash.
  • 🐛📟 vscode-PowerShell #1790 - Fix an inconsistency where Read-Host -Prompt 'prompt' would return $null rather than empty string when given no input.
  • 🐛🔗 PowerShellEditorServices #1177 - Fix an issue where untitled files did not work with CodeLens.
  • ⚡️⏱️ PowerShellEditorServices #1172 - Improve async/await and Task usage to reduce concurrency overhead and improve performance.
  • 🐛📟 PowerShellEditorServices #1178 - Improve PSReadLine experience where no new line is rendered in the console.
  • 🔍 PowerShellEditorServices #1119 - Enable new debugging APIs added in PowerShell 7, improving performance and fixing issues where the debugger would hang or be unable to update breakpoints while scripts were running.
  • 👷📟 PowerShellEditorServices #1187 - Upgrade built-in PSReadLine to 2.0.0 GA.
  • 🐛👮 PowerShellEditorServices #1179 - Improve integration with PSScriptAnalyzer, improving performance, fixing an error when PSScriptAnalyzer is not available, fix CodeActions not appearing on Windows, fix an issue where the PSModulePath is reset by PSScriptAnalyzer opening new runspaces.
  • 🚂 PowerShellEditorServices #1183 - Close over public APIs not intended for external use and replace with new, async-friendly APIs.


Monday, January 13, 2020




Wednesday, December 11, 2019




Friday, November 1, 2019

Special Note

In this release of the preview extension, we've merged significant architectural work into PowerShell Editor Services. After several months of work, PSES now uses the Omnisharp LSP library to handle Language Server Protocol interaction instead of rolling its own, allowing PSES to concentrate on being a good PowerShell backend. We hope you'll see increased performance and stability in this release. As always, please let us know if you find any issues.




Wednesday, May 22, 2019




Wednesday, April 10, 2019


  • vscode-PowerShell #1838 - Set PSReadLine featureFlag default to null so that it can be resolved by settings
  • vscode-PowerShell #1825 - Switch to current lowercase names for powershell and mdlint recommended extensions (Thanks @rkeithhill!)
  • vscode-PowerShell #1823 - Update to official TSLint ext in extensions.json, old version deprecated (Thanks @rkeithhill!)


  • PowerShellEditorServices #909 - Use global.json to pin .Net Core SDK version and update it from 2.1.402 to 2.1.602 (Thanks @bergmeister!)
  • PowerShellEditorServices #903 - Move temp folder into repo to avoid state that causes build errors from time to time when rebuilding locally (and packages have updated) (Thanks @bergmeister!)


Friday, March 29, 2019


  • Write-Progress work in the integrated console
  • Support for PSScriptAnalyzer 1.18 📝
  • The ability to debug any runspace in any process 🔎
  • PSReadLine enabled by default on Windows 🎨
  • (Bug fix!) You can open untitled workspaces/folders again! 🐛☠️

There are a lot more goodies in this version. Checkout the changelog below!



  • PowerShellEditorServices #858 - Fix XUnit warnings that better assertion operators should be used. (Thanks @bergmeister!)
  • PowerShellEditorServices #859 - Upgrade PowerShellStandard.Library, PowerShell.SDK, NET.Test.SDK and Serilog NuGet packages to latest released version and enable AppVeyor build on any branch (Thanks @bergmeister!)


Wednesday, January 23, 2019

Preview builds of the PowerShell extension are now available in VSCode

We are excited to announce the PowerShell Preview extension in the VSCode marketplace! The PowerShell Preview extension allows users on Windows PowerShell 5.1 and PowerShell Core 6 to get and test the latest updates to the PowerShell extension and comes with some exciting features.

The PowerShell Preview extension is a substitute for the PowerShell extension so both the PowerShell extension and the PowerShell Preview extension should not be enabled at the same time.

By having a preview channel, in addition to our existing stable channel, we can get new features out faster and get feedback faster from you, the users.

How to Get/Use the PowerShell Preview extension

If you dont already have VSCode, start here.

Once you have VSCode open, click Clt+Shift+X to open the extensions marketplace. Next, type PowerShell Preview in the search bar. Click Install on the PowerShell Preview page. Finally, click Reload in order to refresh VSCode.

If you already have the PowerShell extension, please disable it to use the Powershell Preview extension. To disable the PowerShell extension, find it in the Extensions sidebar view, specifically under the list of Enabled extensions, Right-click on the PowerShell extension and select Disable. Please note that it is important to only have either the PowerShell extension or the PowerShell Preview extension enabled at one time. How to Disable

What the first preview contains

The v2.0.0-preview.1 version of the extension is built on .NET Standard (enabling support for both Windows PowerShell and PowerShell Core from one assembly)

It also contains PSReadLine support in the integrated console for Windows behind a feature flag. PSReadLine provides a consistent and rich interactive experience, including syntax coloring and multi-line editing and history, in the PowerShell console, in Cloud Shell, and now in VSCode terminal. For more information on the benefits of PSReadLine, check out their documentation.

HUGE thanks to @SeeminglyScience for all his amazing work getting PSReadLine working in PowerShell Editor Services!

Breaking Changes

As stated above, this version of the PowerShell extension only works with Windows PowerShell versions 5.1 and PowerShell Core 6.