Using Visual Studio Code as Your Default PowerShell Editor
summary
VS Code plus the PowerShell extension delivers concrete features: F5 debugging with breakpoints, variable inspection and launch.json configs; Intellisense, snippets and tab-completion; editor/console bridges like PSEdit/openEditorFile and newEditorFile; ScriptAnalyzer integration including ScriptAnalyzer compatibility rules that check target PowerShell versions (3, 5, 6.2); Pester test CodeLens and debug tests; accessibility-friendly session restart and bug-upload flow with logs; experimental psreadline in preview and a custom CodeLens for build tasks that the preview extension already runs.
AI-written summary · about
chapters (29)
- 0:00Start
- 0:16Using Visual Studio Code as Your Default Powershell Editor
- 1:46What Is Visual Studio Code
- 3:15Visual Studio Code
- 3:39Vs Code Is Not Visual Studio
- 4:16The Powershell Extension for Vs Code
- 5:34Intellisense
- 7:02References Code Lens
- 9:24Ps Edit
- 10:17New Editor File
- 11:56Debugging
- 15:57Debug Configurations
- 19:19Integration with Script Analyzer
- 21:14Compatibility Rules in Script Analyzer
- 21:48Script Analyzer Settings File
- 25:47Script Analyzer Integration
- 27:03Ise Compatibility
- 28:00Tab Completion
- 29:40Presenter View
- 30:59Enabling It as the Default Language
- 32:35Troubleshooting
- 33:16Upload a Bug Report
- 33:26Upload Bug Report to Github
- 33:49Upload the Logs
- 34:29Write Progress
- 35:14Psreadline
- 37:54Custom Code Lenses
- 38:22Invoke Build
- 42:05Vs Code Extension Is Open Source
related talks
46mOptimizing Visual Studio Code for Powershell Development
01h 32mOptimizing Visual Studio Code for PowerShell, 2023 Edition
01h 14mCreating a PowerShell Editor
32mA brief history and overview
59mUnleash the Power of Visual Studio Code
01h 33mThe Guts of the PowerShell VSCode Extension
01h 00mUnleash the Power of VS Code
30mWhat's New in Visual Studio Code - Remote Dev, IntelliSense, Build/Debug...