In this video, I go over how to create basic user input controls for your PowerShell-based website. We look at how you can take input from users and execute PowerShell scripts based on that input.
In this video, I demonstrate how to build Windows Forms in VS Code with PowerShell and the PowerShell Pro Tools Windows Forms Designer.
Fixed an issue with parameters passed to packaged scripts
A change made to the $PSScriptRoot support broke the ability to use a param() block in a packaged script. This has been resolved and you should be able to pass parameters to a packaged script again.
Fixed an issue with the installer cmdlets missing dependencies
The Wix binaries were not being installed with the PowerShell Pro Tools module. When attempting to run New-Installer, it would fail and complain about missing candle.exe or light.exe.
Improved the First Time User Experience with the VS Code Forms Designer
The VS Code forms designer will now insert code into the primary form file to help get started with running the form. This includes loading the System.Windows.Forms assembly, dot-sourcing the designer file and calling ShowDialog() on the form.
On February 5th, I presented to the Arizona PowerShell User Group. We went over all the cool features of PowerShell Universal Dashboard.
If you missed the live session, you can check out the recording here.
A Note about Versioning
All the PowerShell Pro Tools and PowerShell Tools for Visual Studio versions are now the same. The reason for this change is the same underlying code is found in each of the tools and having separate version numbers makes it confusing to tell what is in each build. All tools are now on version 4.1.7 and will increase in version with each other. This also means a single set of release notes.
Fixed an Issue where $PSScriptRoot would be $null after packaging
Due to the way that the packager executes bundled scripts, it would result in $PSScriptRoot being $null. A change has been made to ensure that when running a bundled executable that the scripts will have $PSScriptRoot defined to the current directory of the assembly that is executing. This means you should be able to load other resources easier with packaged scripts.
Fixed an Issue where file properties would not be honored by Merge-Script
When packaging an executable you can define properties such as file version and product name. When using a Merge-Script configuration, these options were not being honored and the resulting executable would not have these properties set.
Correctly Enforce Visual Studio 2017 Version
A change was made that required Visual Studio 2017 version 15.8 or later to be installed when using PowerShell Tools for Visual Studio. This was done to support VS 2019. The extension’s manifest was not updated to support this change so it could be installed into VS 2017 versions before 15.8 which would result in an error when attempting to load the extension.
Welcome to our entirely redesigned website! Our new website provides great functionality, customization and integrations than our previous edition.
The Ironman Software store is integrated directly into this website. You’ll be able to review products and purchase directly through the site. We still offer Credit Card (through Stripe) and PayPal processing for orders. You’ll have a lot more control over your account information. You can create an account or login via the Account link on the menu. This will allow you to do things like review orders and update your name and address .
Frequently Asked Questions
We’ve added a Frequently Asked Questions section for some handy information about our products and company.