Posted on Leave a comment

PowerShell Tools for Visual Studio and PowerShell Pro Tools – 4.1.8 Release Notes

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.

Posted on Leave a comment

PowerShell Tools for Visual Studio and PowerShell Pro Tools – 4.1.7 Release Notes

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.