PowerShell Tools for Visual Studio has been updated! See below for release notes.
- Version 3.0.539
- May, 6th 2017
#83 – Provide Context and It block test in Test Explorer
Pester Context and It blocks are now shown in the Test Explorer window. You can now sort the tests by “Namespace” and “Class” which equate to Describe and Context blocks.
Note: Pester only supports running tests at the Describe level. When you execute a Context or It block, it will actually run all the tests in the Describe block and return only the results of the selected tests.
#125 – Cannot drag & drop projects into Solution Folders
Fixed an issue where dragging and dropping a PowerShell project into a solution folder would not work.
#279 – Start debug does not reload PS Session
A configuration option is now available in Tools->Options->PowerShell Tools to reset the PowerShell session before each execution. The PowerShell host process is actually terminated so any loaded DLLs, modules or defined variables will no longer exist in the subsequent sessions. The REPL window is affected but executing commands in the REPL window will not cause the session to reset.
#324 – Interactive Window defaults to C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE>
The PowerShell host now follows the current solution path around. When you open a new solution, the PowerShell host will change directory to the solution folder. When reloading of PS Sessions is enabled, before execution, the PowerShell host will change directory back to the solution directory.
#424 – Can’t open files with .sql extension
Fixed an issue where opening SQL files in a PowerShell project would present a “Value does not fall within the expected range” message box.
Release notes window is now shown after updating PowerShell Tools. Can be disabled in Tools->Options->PowerShell Tools.
Version 1.0.54 (vs2015) and 1.0.52 (VS2017)
May 6th, 2017
Forms Designer Support
PowerShell projects now support the Windows Forms designer and can create forms based on PowerShell script. PowerShell item template is now available to create PowerShell form items.
WPF Designer Support (Beta)
PowerShell projects now support WPF designer with PowerShell script code behind. PowerShell item template is now available to create PowerShell WPF windows.
- WPF designer does not support controls that are not named.
- Generated UI may not be responsive due to the lack of dispatcher implementation.
- WPF designer does not generate variables for all named controls.