{"id":15529,"date":"2018-08-14T08:00:21","date_gmt":"2018-08-14T15:00:21","guid":{"rendered":"https:\/\/www.sapien.com\/blog\/?p=15529"},"modified":"2018-08-14T07:53:36","modified_gmt":"2018-08-14T14:53:36","slug":"powershell-studio-2018-service-release-v5-5-154-and-pscore-support","status":"publish","type":"post","link":"https:\/\/dev.sapien.com\/blog\/2018\/08\/14\/powershell-studio-2018-service-release-v5-5-154-and-pscore-support\/","title":{"rendered":"PowerShell Studio 2018: Service Release v5.5.154 and PSCore Support"},"content":{"rendered":"

We released a new service build of PowerShell Studio 2018 (v5.5.154). This service build is included as part of the regular update cycle for our subscribers.<\/p>\n

 <\/p>\n

New Features<\/h2>\n

This service release adds PowerShell Core (V6) support and introduces several new project features.<\/p>\n

 <\/p>\n

PowerShell Core (V6) Support<\/h3>\n

We are happy to announce added support for PowerShell Core (V6). Now you can select PowerShell Core from the platform selection in the ribbon (Home > Platform):<\/p>\n

\"Platform<\/a><\/p>\n

 <\/p>\n

Note: PowerShell Studio automatically detects preview and release versions of PowerShell Core and displays them in the platform list.<\/p>\n

 <\/p>\n

The new platform settings allow you to run PowerShell Core scripts directly from PowerShell Studio:<\/p>\n

\"Run<\/a><\/p>\n

 <\/p>\n

Important: Debugging and caching for PowerShell Core is not available at this time. For syntax coloring, PowerShell Studio will use the PowerShell V5 cmdlet cache as a fall back.<\/span><\/p>\n

 <\/p>\n

PowerShell Core Consoles<\/h4>\n

In regards to the embedded consoles, if you install a new version of PowerShell Core, you will need to reset your consoles to see the new version in the console panel:<\/p>\n

\"Options<\/a><\/p>\n

 <\/p>\n

If you don\u2019t want to reset any custom settings, then you will have to manually update the path to the PowerShell Core executable.<\/p>\n

 <\/p>\n

Project Features<\/h3>\n

This release introduces several new project specific features.<\/p>\n

 <\/p>\n

Module Projects \u2013 Auto Export Functions and PS1XML files<\/h4>\n

The new auto export features for module projects makes managing your manifest exports easier than ever.<\/p>\n

 <\/p>\n

New Module Project Properties:<\/h5>\n\n\n\n\n\n
Property<\/strong><\/td>\nDescription<\/strong><\/td>\n<\/tr>\n
Auto Export Functions<\/td>\nHandles function exports automatically.<\/td>\n<\/tr>\n
Auto Export PS1XML Files<\/td>\nHandles ps1xml exports automatically.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

 <\/p>\n

\"Module<\/a><\/p>\n

 <\/p>\n

Auto Export Functions<\/h5>\n

If set to True<\/em>, on build, the module project will update the manifest\u2019s FunctionsToExport<\/em><\/strong> field with a list of exported functions. To determine which functions are exported, the module project files have a new Export Functions<\/strong> property that determines if functions defined in the file are exported:<\/p>\n

 <\/p>\n

Project File – Export Functions Property<\/h5>\n

If a project file\u2019s Export Functions<\/strong> property is set to True<\/em>, PowerShell Studio will use the functions defined in the file to update the manifest\u2019s FunctionsToExport<\/em><\/strong> value.<\/p>\n

\"Project<\/a><\/p>\n

 <\/p>\n

This property allows you to organize your functions into files that are public (exported) and private (not exported). Once configured, you do not need to manually update the manifest when you add, remove, or renamed a function.<\/p>\n

 <\/p>\n

Auto Export PS1XML Files<\/h5>\n

If set to True<\/em>, on build, the module project will update the manifest\u2019s TypesToProcess<\/strong><\/em> and FormatsToProcess<\/em><\/strong> fields with the list of ps1xml files contained within the project.<\/p>\n

Depending on the file\u2019s name, PowerShell Studio will determine which field to use:<\/p>\n\n\n\n\n\n
Filename<\/strong><\/td>\nManifest Field<\/strong><\/td>\n<\/tr>\n
*.Type.ps1xml<\/td>\nTypesToProcess<\/td>\n<\/tr>\n
*.Format.ps1xml<\/td>\nFormatsToProcess<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Note: The ps1xml file must be part of the project and its Build<\/strong> property must be set to Content<\/em> in order for it to be included in the manifest.<\/p>\n

 <\/p>\n

When you Build<\/em> the module project the manifest is now updated automatically, thus alleviating the previous requirement to manually update the manifest.<\/p>\n

\"Module<\/a><\/p>\n

 <\/p>\n

Build Order<\/h4>\n

The new project file Build Order<\/strong> property allows you to determine the order in which project files are merged into the final project script. This setting only applies to project files with the Build<\/strong> property set to Include<\/em>.<\/p>\n

\"Project<\/a><\/p>\n

The build order can be important when the content of one project file is dependent on the content of another file.\u00a0 For example, when dealing with class inheritance in PowerShell, you must make sure the base class is defined before declaring any classes that inherit from that base class. By setting the build order of the individual class files, you can ensure that the final script includes the base class definition before the inherited class definition.<\/p>\n

Another use case would be when functions or global variables are defined within a global file (Shared<\/b> = True<\/i>). To ensure those declarations are defined before invoking, the build order index should be set to a value lower than that of the dependent project files.<\/p>\n

 <\/p>\n

Set the build order of project files by modifying the zero-based index of each project file. An index of 0<\/strong> ensures that the file will be the first one merged into the generated script.<\/p>\n

 <\/p>\n

There are some exceptions to the build order:<\/p>\n

– In a module project, the primary psm1 file\u2019s content is included at the end of the generated script regardless of its Build Order<\/strong> property value.<\/p>\n

– Collection projects only support project files with Build<\/strong> = Content<\/em>, therefore the Build Order <\/strong>property is not applicable.<\/p>\n

 <\/p>\n

Project Sync on Activate<\/h4>\n

We included a new option, Sync files when the application is activated<\/em>, that allows you to trigger project file synchronization when the application regains focus (activated).<\/p>\n

Options > General > Project:<\/p>\n

\"Sync<\/a><\/p>\n

Note: In order for this feature to work, you must have a project opened with file synchronization enabled (Synchronized<\/strong> = True<\/em>):<\/p>\n

\"Project<\/a><\/p>\n

This option ensures that the application can detect changes when you are making modifications to the project\u2019s folder structure outside of PowerShell Studio.<\/p>\n

\"Files<\/a><\/p>\n

Note: We updated the synchronization messages to use +<\/strong> and \u2013<\/strong> for adding and removing file messages.<\/p>\n

 <\/p>\n

Windows Service Project Template<\/h4>\n

This service release includes the new Windows Service Project<\/em> template which allows you to create a Windows service script using a project:<\/p>\n

\"Windows<\/a><\/p>\n

Some benefits of using a project verses a single file script are the ability to manage additional content, and also to organize your script into individual script files to make your code more manageable.<\/p>\n

\"Windows<\/a><\/p>\n

The Windows Service Project <\/i>utilizes the same predefined functions used by the single file Windows Service Script template.<\/p>\n

 <\/p>\n

PowerShell Browser \u2013 Distinguishing Command Types<\/h3>\n

We updated the PowerShell Brower in the Object Browser Panel, so that the icons visually distinguish functions, workflows, and cmdlets:<\/p>\n

\"Object<\/a><\/p>\n

 <\/p>\n

This change helps surface the true command types of the module. In addition, the PowerShell Browser now retains your selection when switching between PowerShell platforms.<\/p>\n

 <\/p>\n

PS1XML Type Caching<\/h3>\n

PowerShell Studio now caches ps1xml type files, which allows PowerShell Studio\u2019s PrimalSense to display extended type properties and methods without executing the script.<\/p>\n

\"PrimalSense<\/a><\/p>\n

 <\/p>\n

Feedback<\/h2>\n

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<\/a> forum or the new Feature Requests<\/a> page.<\/p>\n

You can view the complete service build log here<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"

We released a new service build of PowerShell Studio 2018 (v5.5.154). This service build is included as part of the regular update cycle for our subscribers.   New Features This service release adds PowerShell Core (V6) support and introduces several new project features.   PowerShell Core (V6) Support We are happy to announce added support […]<\/p>\n","protected":false},"author":10,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"categories":[703,21,632],"tags":[28,1215,1244,645,155,141],"class_list":["post-15529","post","type-post","status-publish","format-standard","hentry","category-powershell-studio","category-software-news","category-whats-new-software-news","tag-powershell","tag-powershell-core","tag-powershell-studio-2018","tag-service-build-2","tag-service-release","tag-whats-new"],"jetpack_featured_media_url":"","_links":{"self":[{"href":"https:\/\/dev.sapien.com\/blog\/wp-json\/wp\/v2\/posts\/15529","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/dev.sapien.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/dev.sapien.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/dev.sapien.com\/blog\/wp-json\/wp\/v2\/users\/10"}],"replies":[{"embeddable":true,"href":"https:\/\/dev.sapien.com\/blog\/wp-json\/wp\/v2\/comments?post=15529"}],"version-history":[{"count":8,"href":"https:\/\/dev.sapien.com\/blog\/wp-json\/wp\/v2\/posts\/15529\/revisions"}],"predecessor-version":[{"id":15816,"href":"https:\/\/dev.sapien.com\/blog\/wp-json\/wp\/v2\/posts\/15529\/revisions\/15816"}],"wp:attachment":[{"href":"https:\/\/dev.sapien.com\/blog\/wp-json\/wp\/v2\/media?parent=15529"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/dev.sapien.com\/blog\/wp-json\/wp\/v2\/categories?post=15529"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/dev.sapien.com\/blog\/wp-json\/wp\/v2\/tags?post=15529"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}