PowerShell Studio 2017: Service Release v5.4.144

Today we released a new service build of PowerShell Studio 2017 (v5.4.144).

In this service build we made several improvements to PowerShell Studio’s class PrimalSense and refactoring capabilities.

 

New Features

Class PrimalSense

This service release greatly improves PrimalSense support for custom PowerShell classes defined in a script and across files when using a project or when dot sourcing.

PrimalSense for Custom Enumerators:

PrimalSense Enum

 

Constructor PrimalSense:

PrimalSense Constructors

Press the TAB button to auto-insert the parameters.

 

Class Members:

PrimalSense Class Members

PrimalSense for $This variable within the class definition:

PrimalSense This

 

You can use the Go to Declaration command on the custom classes and on its class members:

Go To Declaration

 

Refactoring Improvements

In addition to improving PrimalSense support, we also improved rename refactoring and reference highlighting.

You can now refactor a class name:

Refactor Class Name

Or a class member name:

Refactor Class Members

When you refactor a class member, references to that member are updated throughout the script.

Refactor References

 

Find All References

Now you can use the Find All References command to find references to a particular type:

Find All Type References

When working with projects, references found throughout the whole project are displayed.

 

You can now also find references to a particular property or method:

Member References

 

Updated Navigation Bar

We added a new scope dropdown to the editor’s navigation bar. The scope dropdown lets you jump to class or enumerator declarations contained within the file.

Scope Navigation Menu

 

When the caret is within in the scope of a class, the function dropdown is updated to reflect the class’ member declarations.

Navigation Menu Members

 

New Packager Restriction

We added a new packager restriction option:

Disable script block transcripts while running

When this option is checked, the packager engine will attempt to disable transcripts before executing the script. Use this option when you wish to protect sensitive scripts.

Packager - Disable transcripts

 

We hope these new features improve your overall experience with PowerShell Studio. 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.

You can view the complete service build log here.