In this video, I demonstrate how to use the code conversion engine provided by PowerShell Pro Tools for Visual Studio Code. You can select C# code and convert it to PowerShell by using the Convert To PowerShell command.
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
Fixed Resource Bundling for the Visual Studio Windows Form Designer
The resource file was not being properly generated when building WinForms in Visual Studio. This caused errors to be shown when running a form and the resources, such as icons, would
Fixed issues with Copy command in PowerShell Interactive Window
An error would be show if right clicking to copy from the interactive window. Attempting to copy text that was not part of the command line would fail to copy.
Added system requirements
The Ctrl+C Copy Now Works in the PowerShell Interactive Window (Visual Studio)
Ctrl+C now supports cancelling a currently executing command in the interactive window as well as the ability to copy text from the interactive window.
Improved Task List Implementation (Visual Studio)