We released a new service build for PowerShell Studio 2016 (v4.2.118).
Here’s what’s new:
Support for PSScriptAnalyzer module
PSScriptAnalyzer module is a community driven module that evaluates your PowerShell scripts and ensures they follow community approved best practices.
PowerShell Studio 2016 now allows you to run PSScriptAnalyzer directly from the ribbon (Tools->Analysis->Analyze Script):
Note: This option will be disabled if the PSScriptAnalyzer is not installed.
When you use the Analyze Script command, the module results are displayed in the Debug Panel:
Jump to the respective line in the script by double-clicking on result.
PowerShell Studio 2016 also includes an option to trigger PSScriptAnalyzer every time you run / debug a PowerShell script or a project (Options->Editor):
Now when you test your scripts, the analysis is automatically displayed in the Debug panel.
We added the option to display whitespaces in the editor.
This feature should help you spot those unintentional (and annoying) white spaces that trail behind a back tick at the end of a line.
Preventive Measures in Packager Executables
We added some preventive measures to help deter unwanted debugging of your package executables. You can further help improve the security of your executables by enabling restrictions in the packager settings to ensure they do not run on unauthorized machines.
Please continue providing your feedback. Many of the new features included in the service builds are suggestions from users like you. Therefore if you have any suggestions or feature requests, please share them with us on our Wish List and Feature Requests forum.