Visual Studio: 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
Visual Studio: 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.
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
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
Improved Performance of PSScriptAnalyzer Support
The performance of PSScriptAnalyzer has been improved by moving the analysis into a background runspace within the PowerShell host process. The classification service will no longer wait for a script analyzer to run when typing.
Improved the performance of output
Moved host output from simple gRPC RPC calls to a streaming call which greatly improves the performance of output.
Fixed an issue where you couldn’t delete a folder
Due to a misconfiguration of the PowerShell project type, folders
Added the ability to package the PowerShell 7 engine with executables
Added an option on the PowerShell Project Advanced page to allow for packaging PowerShell 7 with the executable.
Stand Alone Windows Form Designer
Fixed a potential null reference exception inside the IntelliSense feature
If IntelliSense is used before the PowerShell Tools package has completely loaded, an object reference will be shown.
Fixed issue with license check on none-English operating systems
An invalid DateTime error would be
Fixed issue with Write-Progress
Write-Progress would throw an error when running in the new PowerShell host.
Additional Logging to PowerShell Host and Host Startup
Additional logging has been added to help diagnosis startup issues. Logging will be written to:
%AppData%\PowerShell Tools for Visual Studio
PowerShell Pro Tools now supports PowerShell 6 and 7
With PowerShell Pro Tools, You can now switch between Windows PowerShell and PowerShell 6 and 7. The PowerShell Tools for Visual Studio host now works with .NET Core and can run