Why PowerShell Pro Tools for VS Code?
User Interface Design
Take advantage of the PowerShell Pro Tools Windows Form designer in Visual Studio Code. Easily drag and drop controls, set properties and add event handlers.
Package scripts as executables. Bundle in modules, assemblies and XAML files. Include the PowerShell 6 or 7 runtime directly in your executable so there is no need to install .NET Core or PowerShell on target machines.
Profile the performance of your scripts directly in Visual Studio Code to see line by line execution time and call counts. Quickly identify slow sections of code.
Easily view and upgrade the modules that are present on your system.
Convert between C# and PowerShell code to easily take snippets of either language and convert it to the other. Quickly create P\Invoke functions in PowerShell from C# snippets found on sites like Pinvoke.net.
Provider Tree View
Easily travese PowerShell providers by clicking in the PowerShell Explorer window. View the value of items within the providers such as variables and files.
Explore the AST of the current file by using the AST Explorer. View AST nodes and select the text within the editor that corresponds to a particular node.
Quick Scripts allow you to store scripts in your VS Code environment that can be quickly accessed by issuing a command. Quick Scripts are global so no matter where you open VS Code, you’ll be able to access your script.
Licensed per developer
Run on any computer used by that user
Free upgrades for a year
Money Back Guarantee
PowerShell Pro Tools Suite
- Free updates for a year
Frequently Asked Questions
No. PSScriptPad is just an alternative to VS Code. It currently only supports Windows PowerShell and doesn’t have all the features and extensibility you will find in VS Code. That said, it’s much smaller and faster to launch. It’s great for quickly editing and debugging scripts but might not be suitable for working on large projects. That said, it has features that VS Code does not including a Windows Form Designer and script packaging.
PowerShell Pro Tools is licensed per user. Each user will need their own license. That user can use that license on as many machines as they are using but only if they are the sole user.
PowerShell Pro Tools augments PowerShell Tools for Visual Studio and the Visual Studio Code PowerShell extension. Rather than a dedicated PowerShell scripting environment, PowerShell Pro Tools integrates into existing development environments. PowerShell Pro Tools supports GUI creation via Windows Forms, packaging as executables and services and even creating installers, just like Sapien PowerShell Studio. Because PowerShell Pro Tools is built into Visual Studio and Visual Studio Code, you also benefit from all the features of those environments such as Git integration. PowerShell Pro Tools even offers features, such as code conversion, that PowerShell Studio does not.
PowerShell Pro Tools provides a Visual Studio, Visual Studio Code and PowerShell solution. The same license key applies to all three. If you choose to build forms in Visual Studio but package scripts in Visual Studio Code, you can use the same license for each. The license is good for one year of upgrades.