Posted on Leave a comment

PowerShell Tools for Visual Studio and PowerShell Pro Tools – Version 4.4.0 Release Notes

PowerShell Pro Tools – Module Explorer

The PowerShell Pro Tools extension for VS Code now provides a new tree view in the activity bar to view and update modules. It will list all the modules that are currently installed and flag any modules that are out of date. You can then upgrade the module directly from VS Code.

Updating the Polaris Module with the Module Explorer

If you wish to hide the Module Explorer, just change the Module Explorer Visibility setting.

Improved Performance of VS Code Extension

Previously, the VS Code extension would execute all the PowerShell script necessary for its functions in the terminal window. Not only was this slow but it would pollute the history of the terminal. With the 4.4.0 release, the VS Code extension now uses a background runspace for operation. This improves performance and ensures a clean terminal history.

Improved Dependency Check Warnings

The packager requires both .NET Core and the .NET Framework Developer Pack installed to function. Previously, the warning messages were cryptic. These messages have been improved and contain links to where to download the missing dependencies.

Fixed an issue with the Form Designer Licensing

The form designer would reprompt for a license even after it had been installed in VS Code.

Posted on Leave a comment

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

Fixed an issue with detecting .NET Reference Assemblies

The packaging feature requires the .NET Framework Developer Pack to be installed. The packager was incorrectly determining where the installation was. This resulted in package failures without any error message. The packager will now warn when it does not find the proper .NET Developer Pack installed.

Fixed an issue with licensing in VS Code

The licensing change in the previous release broke the license check in the packager.

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.