5.3.4 – 2020-2-10
5.3.3 – 2020-2-4
- Added a PowerShell Windows Forms Project template
- Fixed an issue when setting the platform for a packaged script
- Fixed an issue when setting the “PackagePowerShell” setting for a packaged script
- Fixed a syntax error with the Windows Forms item template
5.3.2 – 2020-1-28
- Fixed issue with resource generation in Visual Studio Windows Forms Designer
- Fixed issue where packaged applications wouldn’t work with arguments with spaces
5.3.1 – 2020-1-22
No longer requires a trial key
5.2.5 – 2020-1-21
Fixed an issue with PowerShell Pro Tools initializing
Depending on how the PowerShell Pro Tools extension was loaded an error would be shown and it would fail to loaded.
5.2.4 – 2020-1-18
Fixed an issue with bundling resources
Resources, such as images and icons, would not be bundled correctly when bundling a WinForm control.
5.2.3 – 2020-1-16
Fixed an issue with license checking for the WinForm designer
If you opened the WinForm designer before installing your license, then installed a license and then opened the WinForm designer, you would need to restart Visual Studio for the license to take effect.
5.2.2 – 2020-1-15
Republished 5.2.1 as 5.2.2
An issue with the marketplace was causing a failure when upgrading to 5.2.1. Republished as 5.2.2 and it seems to have resolved it.
5.2.1 – 2020-1-15
Fixed an issue with license activation
License activation could run more than once causing the product to think that it was unlicensed.
5.2.0 – 2020-1-14
Added Platform Settings to Packaging
You can now specify the platform (x64\x86) when packaging executables.
5.1.4 – 2019-11-21
Fixed Crash During Start up or Solution Load
There was a race condition between the PowerShell host starting and the gRPC client being available to set the location of the REPL window. This would cause a crash when VS was starting and loading a PS solution at the same time.
Fixed Crash when selecting PS Script Analyzer Rules
When selecting PS Script Analyzer rules, there could be a condition where a directory needed to store the settings would not exist. This directory is now created before attempting to save the settings.
Added STA Support for Windows PowerShell
In the General options page, you can now select STA mode for Windows PowerShell. This primarily affects Windows Forms controls, like the web browser control, that rely on COM.
5.1.3 – 2019-11-19
Hang when running command-line tools
Command-line tools that used the error stream (like git.exe) would cause a hang in the PowerShell debugger.
5.1.2 – 2019-11-18
Visual Studio: Fixed Aggressive Extension Loading
The PoshTools extension was loading aggressively. It would load even when no PowerShell solution or interactive window was open.
Visual Studio: Fixed exception in script analyzer
When Visual Studio was loading, the script analyzer would attempt to analyze “null” file resulting in an error.
Visual Studio: Added Convert to PowerShell command
The Paste As command was replaced with Convert to PowerShell.
5.1.1 – 2019-11-15
Visual Studio: Visual Studio would hang when using PowerShell v3\v4
When the PowerShell extension would initialize and PowerShell v3 or v4 was being used, the extension would cause the IDE to hang.
Visual Studio: Debugging would not work in Visual Studio 2017
The error “Attaching the PowerShell Debug Engine debugger to Process unknown process” would be shown when attempting to debug.
Visual Studio: Breakpoint would not be set in Visual Studio 2017
The debugger would not break on a breakpoint set in Visual Studio 2017.
5.1.0 – 2019-11-11
Visual Studio: Solution Wide Analysis
PowerShell Pro Tools now uses PSScriptAnalyzer to analyze all the scripts within your solution in the background. You will still see tags on the active file, but the error list will also report any issues with any PSM1 or PS1 files in your solution.
Visual Studio: PSScriptAnalyzer Settings
You can now modify PSScriptAnalyzer settings directly in the PowerShell Tools Options. Go to the Analysis page to turn on Analysis, Solution Wide Analysis, enable specific levels or even turn off specific rules.
Visual Studio Code: Fixed PowerShell Host Initialization
The PowerShell Pro Tools host could fail to initialize so startup operations would not be performed putting the extension in an unknown state. The extension has been fixed to load the host consistenlty.
Visual Studio Code: Fixed PowerShell Host Crash Reinitialization
If the Visual Code PowerShell Host would crash, PowerShell Pro Tools would not reconnect to the PowerShell process. This would prevent it from working.