KB3002 - PowerShell Pro Tools for VS Code (2002) stopped working
Scope
This is a legacy article which only applies to PowerShell Pro Tools for VS Code version 2022.7.2 and below
If your PowerShell Pro Tools for VS Code is at 2022.8.0 or higher then this article does not apply
Problem
PowerShell Pro Tools extension for VS Code was working fine until July 29th, 2022 when the Microsoft PowerShell extension was updated to v2022.7.2*
Root Cause
Microsoft broke certain functionalities in extensions with the release of their VS Code extension 7.2 (the version jumped from 6.3 to 7.2). See comments from Adam Driscoll around this at https://forums.ironmansoftware.com/t/powershellpro-tools-extension-installed-but-throws-error/7513
Solution for Subscribed Users
Upgrade to PowerShell Pro Tools to version 8.0 (or higher) where this problem was addressed on August 9th, 2022**
Workaround for Perpetual License Users
If your perpetual license expired before August 9th, 2022 then your only option is to downgrade the Microsoft PowerShell extension from 7.2+ back down to 6.3 and stay with that forever
Select 2022.6.3 from ‘Install Another Version’ under the extension settings (pictured below).
Direct link to the extension: ms-vscode.PowerShell-2022.6.3.vsix (20.6 MB)
If your perpetual license expired after August 9th, 2022 then you should be able to select a version of the PowerShell Pro Tools extension for Vs Code that is of version 8.0 or higher (pictured below).
Related Articles
KB3010 - PowerShell Pro Tools for VS Code "command not found"
Scope This article only applies to PowerShell Pro Tools for VS Code on the Windows operating system. If you are using PowerShell Pro Tools for VS Code for Mac or Linux then this article does not apply Problem The PowerShell Pro Tools extension for VS ...KB3003 - Resetting PowerShell Pro Tools (VS Code)
Problem PowerShell Pro Tools (for VS Code) is not behaving as expected. For example, pressing the 'Show Form Designer' button does not successfully launch PSScriptPad (only the splash screen is shown). Solution This solution assumes that you have VS ...KB3009 - PowerShell Pro Tools for VS Code "failed to connect"
Scope This article only applies to PowerShell Pro Tools for VS Code on the Windows operating system. If you are using PowerShell Pro Tools for VS Code for Mac or Linux then this article does not apply Problem The PowerShell Pro Tools extension for VS ...KB3012 - PowerShell Pro Tools feature not working
Scope This article only applies to features of PowerShell Pro Tools for VS Code. Problem A feature (e.g. Refactoring) doesn't work even though you expect it to. Symptoms No action occurs when invoking one of the PowerShell Pro Tools features from the ...KB3008 - About PowerShell Pro Tools Licensing
Scope Anyone who has purchased a license for PowerShell Pro Tools Question How many machines can I install PowerShell Pro Tools (PowerShell module, PowerShell Pro Tools for VS. Code or PowerShell Tools for Visual Studio? Answer PowerShell Pro Tools ...