Today we released a new service build of PowerShell Studio 2018 (v5.5.149). This service build is included as part of the regular update cycle for our subscribers.
Important: Please update to this build in order to resolve the unhandled exception issues introduced in the v5.5.148 build.
New Features
This service release introduces a new line ending feature and updates the form file (psf) version.
File Line Endings
You can now use PowerShell Studio’s status bar to view line ending of the active file:
To change the line ending, click on the line ending display in the status bar and select the desired settings from the pop-up menu:
You can choose from the following options:
| Option | Description | OS |
| CR LF | Carriage Return New Line | Windows |
| LF | New Line | Unix |
With the LF option, you can configure PowerShell scripts for Unix based machines that use PowerShell Core (v6).
Note: If you change the line ending of a form file (psf), PowerShell Studio will use the same line ending setting when exporting scripts from the psf file.
PSF File Version Update
In this service build, the psf file was updated to preserve the key names of images in an ImageList and to resolve serialization issues with the TreeView control’s TreeNodes, where the ImageIndex property did not persist in the saved file. Because of these structural changes, the new psf version is not backwards compatible with older builds of PowerShell Studio.
When opening an older version psf file, PowerShell Studio will display a warning:
The warning notifies you that the file version will be updated on save. As a precaution, PowerShell Studio will create a backup of the original file before updating to the latest version.
The backup file will be created in the same directory as the psf file using a bak extension:
FileName.psf.bak
Feedback
Please continue providing your feedback. Many of the new features included in the service builds are suggestions from users like you. Submit your suggestions or feature requests on the Wish List and Feature Requests forum or the new Feature Requests page.
You can view the complete service build log here.
