Microsoft Updates VS Code PowerShell Extension with Major Overhaul of PowerShell Editor Services
Microsoft's development team released a two‑year, user‑driven overhaul of the VS Code PowerShell extension, redesigning the PowerShell Editor Services engine, introducing a new thread model, adding 6,000 lines of code, removing 12,000, and improving stability, performance, and developer feedback mechanisms.
Microsoft's development team recently released a major two‑year update to the PowerShell extension for Visual Studio Code, driven by user feedback submitted via GitHub issues.
According to Microsoft staff member Sydney Smith, the update represents a complete redesign of the PowerShell Editor Services core engine to provide a more reliable and stable user experience.
The PowerShell Editor Services, which implements a Language Server Protocol (LSP) server, now uses a new dedicated pipeline thread that leverages JavaScript's event loop, eliminating previous asymmetries between the synchronous PowerShell runtime and the asynchronous LSP service.
Previously, the Integrated Console ran on a shared thread‑pool task in the main process, causing overhead and race‑condition issues; the new model separates the console and LSP handling, improving reliability.
The release added roughly 6,000 lines of code and removed about 12,000 lines, making the backend easier to maintain, more efficient, and easier to understand.
In the past six months Microsoft published 13 PowerShell preview builds for testing; the stable extension has been installed about 5.8 million times with an average rating of 3.7/5, while the preview has over 200,000 installs and a 4.6/5 rating.
Full change details are available in the extension's changelog , and developers can submit bugs or feature requests via the project's GitHub page.
IT Services Circle
Delivering cutting-edge internet insights and practical learning resources. We're a passionate and principled IT media platform.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.