A brief history and overview
summary
Nine years of the PowerShell extension for VS Code get compressed into concrete wins: first commit in October 2015, PSReadLine support landed via PR #6722, a multi‑year V3 rewrite finishes in 2022, regression tests now exercise vim and emacs, fixes remove the Mac “typewriter” paste, completions race conditions and ghost terminals, added dev tunnels/port forwarding and 4,860 pull requests bring compatibility with VS Code API v1.82 — features shipped and many longstanding bugs actually get fixed.
AI-written summary · about
chapters (8)
- 0:00PowerShell extension intro
- 1:28Early development
- 3:11Milestones and maintainers
- 5:39Rewriting Editor Services
- 8:04Beyond VS Code
- 10:32Quality and stability focus
- 12:18VS Code demos
- 25:52Q&A
related talks
01h 32mOptimizing Visual Studio Code for PowerShell, 2023 Edition
45myear of improvements to your PowerShell editing experience
44mUsing Visual Studio Code as Your Default PowerShell Editor
01h 33mThe Guts of the PowerShell VSCode Extension
46mOptimizing Visual Studio Code for Powershell Development
41mThe evolution of DevX
43mPowerShell Tooling
59mUnleash the Power of Visual Studio Code