Creating a PowerShell Editor
summary
Builds a working PowerShell editor using the PowerShell SDK for hosting and parser/completion, an Avalonia UI with Avalonia Edit and TextMate grammars for syntax highlighting, and PSScriptAnalyzer for linting; code completion uses CommandCompletion and once hit a case with 150 completion matches. Shows running scripts from the editor and how to switch to the PowerShell Editor Services LSP over named pipes so editors get completion, diagnostics and fixes with far less manual plumbing; the hand‑rolled editor is functional but slow, LSP approach is cleaner.
AI-written summary · about
chapters (16)
- 0:00PowerShell editor intro
- 3:28Editing concepts & approaches
- 7:39Hosting PowerShell & parsing
- 12:57Avalonia editor setup
- 23:02Basic editor demo
- 26:49PowerShell syntax highlighting
- 27:10PowerShell SDK for completion
- 35:29Syntax error detection
- 39:21PSScriptAnalyzer integration
- 48:24Script execution in editor
- 51:19Language Server Protocol
- 52:01How LSP simplifies editor development
- 57:18VS extension with LSP
- 1:05:03Testing VS extension
- 1:07:32VS Code extension overview
- 1:11:23Resources & Q&A
related talks
44mUsing Visual Studio Code as Your Default PowerShell Editor
45mInteractive Enhancements to PowerShell
01h 33mThe Guts of the PowerShell VSCode Extension
01h 32mOptimizing Visual Studio Code for PowerShell, 2023 Edition
46mPSScriptAnalyzer (PSSA) VS-code integration & customization Compatibility Analysis
36mSapien PowerShell Products
45myear of improvements to your PowerShell editing experience
39mShell Enhancements