KB3008 - About PowerShell Pro Tools Licensing

KB3008 - About PowerShell Pro Tools Licensing

Scope

Anyone who is considering purchasing a PowerShell Pro Tools License.

Problem

You are not sure which PowerShell Pro Tools license is best for you or your organization. 

Solution

See the below flowchart that covers all licensee scenarios. 





    • Related Articles

    • KB3005 - Troubleshooting License Issues

      Purpose The purpose of this article is to explain in technical detail how to workaround when the license for PowerShell Pro Tools won't install (figure shows how an Ironman Software license file should appear in a text viewer) Affected Products ...

    • 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 ...

    • 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 ...

    • 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 ...