https://www.seanross.us/categories/workflow/Recent content in Workflow on Sean RossHugoenThu, 28 May 2026 00:00:00 +0000https://www.seanross.us/posts/your-editor-is-a-client/Thu, 28 May 2026 00:00:00 +0000https://www.seanross.us/posts/your-editor-is-a-client/<h2 id="why-vs-code-for-powershell"> Why VS Code for PowerShell? <a class="heading-link" href="#why-vs-code-for-powershell"> <i class="fa-solid fa-link" aria-hidden="true" title="Link to heading"></i> <span class="sr-only">Link to heading</span> </a> </h2> <p>While I can&rsquo;t say I&rsquo;ve ever been a fan of the ISE, it has long been relied on by PowerShell enthusiasts and admins alike. Since Microsoft deprecated the ISE, it has pushed users toward VS Code and the PowerShell extension. VS Code and the PowerShell extension do bring a lot of useful features when compared to the dated ISE, but how much of that comes from the editor vs. extension? If VS Code disappeared tomorrow, what would we lose? Which features would we really miss?</p>