Optimizing Visual Studio Code for Powershell Development
summary
Start from a fresh VS Code zip and create a Data folder so the install runs in portable mode; install the PowerShell preview extension, the curated extension pack, plus visual tools like git graph for branch topology and error lens for inline diagnostics. Enable format-on-save-modification and PowerShell’s formatter to reformat only changed lines, add a Nerd Font for ligatures, and install the Pester test extension to run and watch tests inside the editor.
AI-written summary · about
chapters (21)
- 0:00Introduction
- 1:40References
- 3:25Getting Visual Studio Code
- 4:55Portable Mode
- 10:40General Settings
- 16:10Settings Sync
- 17:50Git Graph
- 21:30Git Lens
- 22:50Shortcut Development Loop
- 24:00Nerd Fonts
- 26:10Terminal Fonts
- 28:10Better Align
- 29:10Code Formatting
- 30:20Code Formatting Settings
- 32:10Align Property Values
- 35:20Workspace Settings
- 36:35Debugging Settings
- 38:10Define RunDebug Tasks
- 39:00Sync Settings
- 39:35Closing Tabs
- 42:45Pester Test Extension
related talks
01h 32mOptimizing Visual Studio Code for PowerShell, 2023 Edition
44mUsing Visual Studio Code as Your Default PowerShell Editor
59mUnleash the Power of Visual Studio Code
01h 00mUnleash the Power of VS Code
32mA brief history and overview
19mBeyond the Myth: Develop Comfortably on Windows
01h 33mThe Guts of the PowerShell VSCode Extension
48mVisual Studio Code can do that?