{"id":14353,"date":"2018-02-07T08:00:21","date_gmt":"2018-02-07T16:00:21","guid":{"rendered":"https:\/\/www.sapien.com\/blog\/?p=14353"},"modified":"2018-02-05T14:53:39","modified_gmt":"2018-02-05T22:53:39","slug":"powershell-studio-2018-released","status":"publish","type":"post","link":"https:\/\/dev.sapien.com\/blog\/2018\/02\/07\/powershell-studio-2018-released\/","title":{"rendered":"PowerShell Studio 2018: Released!"},"content":{"rendered":"

We are happy to announce the release of PowerShell Studio 2018, which is included as part of the regular update cycle for our subscribers.<\/p>\n

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

 <\/p>\n

New Features and Improvements<\/h2>\n

The 2018 release includes many improvements and new features to enhance your overall experience with PowerShell Studio.<\/p>\n

 <\/p>\n

PrimalSense Improvements<\/h2>\n

<\/h3>\n

Updated Cache<\/h3>\n

We updated our cache to include additional information, such as parameter set names, return values and validation sets.<\/p>\n

Note: Building the new cache will take longer than previous versions due to the inclusion of additional information.<\/em><\/p>\n

 <\/p>\n

Now when you hover over a cmdlet or function, the parameter set information is displayed, including the output types:<\/p>\n

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

Parameter sets with specified output types are displayed accordingly:<\/p>\n

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

 <\/p>\n

PrimalSense can now display a cmdlet\u2019s parameter validation set:<\/p>\n

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

 <\/p>\n

PrimalSense for using<\/em> assembly<\/em> Statements<\/h3>\n

PrimalSense will now provide a list of assemblies for the using<\/span><\/em> statement\u2019s assembly<\/span><\/em> parameter.<\/p>\n

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

<\/h4>\n

Cmdlet PrimalSense for Qualified Modules<\/h3>\n

PowerShell Studio now provides PrimalSense for a module\u2019s cmdlets when using the module\u2019s fully qualified name:<\/p>\n

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

Note: PrimalSense will only display the cmdlets of the specified module.<\/p>\n

 <\/p>\n

Cmdlet Parameter Set Completion<\/h3>\n

When working with a cmdlet or function, you can trigger the parameter set completion pop-up by pressing [Ctrl + Shift + Space]:<\/p>\n

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

The pop-up will present the current parameter set (if it can be determined). When you press [TAB], PowerShell Studio will insert any missing parameters of the designated parameter set:<\/p>\n

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

 <\/p>\n

Customizable Consoles and PowerShell Core<\/h2>\n

You now have the option to configure PowerShell Studio\u2019s embedded consoles (Options->Console):<\/p>\n

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

On the first run, PowerShell Studio will attempt to detect Windows PowerShell and PowerShell Core and automatically add them to the console list.<\/p>\n

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

If the need arises, you can reset the consoles back to the default PowerShell consoles by pressing the Reset<\/strong> button:<\/p>\n

\"Reset<\/a><\/h3>\n

 <\/p>\n

New Code Folding Option \u2013 Functions<\/h2>\n

PowerShell Studio 2018 added a new Functions<\/em> option to code folding. The new Functions<\/em> option will collapse and expand function declarations separately from script blocks:<\/p>\n

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

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

Note: The Script Blocks <\/em>option now only applies to script blocks that are not part of a function declaration.<\/p>\n

 <\/p>\n

Formatting \u2013 Reserved Word Casing<\/h2>\n

We added a new formatting option that allows you to format reserved word (keyword) character casing in Options->Formatting:<\/p>\n

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

You can select from the following options:<\/p>\n\n\n\n\n\n\n
None<\/strong><\/em><\/td>\nLeaves the reserved word casing as is.<\/td>\n<\/tr>\n
Upper<\/em><\/strong><\/td>\nUses all upper-case characters:
\nIF
\nIFELSE
\nWHILE<\/span><\/td>\n<\/tr>\n
Lower<\/em><\/strong><\/td>\nUses all lower-case characters:
\nif
\nifelse
\nwhile<\/span><\/td>\n<\/tr>\n
Camel<\/em><\/strong><\/td>\nUses camel case characters:
\nIf
\nIfElse
\nWhile<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

 <\/p>\n

Output Panel \u2013 Coloring<\/h2>\n

PowerShell Studio will now change the color of the text to denote errors and warnings in the Output and Debug Panels, making important messages stand out.
\n\"Colored<\/a><\/p>\n

PSScriptAnalyzer<\/em> results are now color-coded as well:<\/p>\n

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

 <\/p>\n

Copy Encoded<\/h2>\n

We added a new Copy Encoded<\/strong> command (Ribbon->Home->Clipboard) that will Base64 encode the selected text and copy it to the clipboard:<\/p>\n

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

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

 <\/p>\n

Remote Console Prompt<\/h2>\n

We\u2019ve made it easy to create a new remote console session to any machine at any time. Now when you press the Remote Console button, and the Local Machine is selected in the platform settings (Ribbon->Home->Platform), PowerShell Studio will prompt you to enter remote credentials:<\/p>\n

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

Previous versions required you to configure a remote machine before you could open a remote console.<\/p>\n

 <\/p>\n

New Variable for Snippets and Templates<\/h2>\n

PowerShell Studio 2018 introduces a new variable for snippets:<\/p>\n

%FileDirectory%<\/strong><\/em><\/p><\/blockquote>\n

Whenever a snippet is triggered that contains this variable, it will insert the directory of the active script:<\/p>\n

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

The %FileDirectory%<\/strong><\/em> variable can also be used in file templates.<\/p>\n

 <\/p>\n

Updated Generated Database Query Script<\/h2>\n

We updated the Database Panel\u2019s generated query scripts to bring them in line with the generated grid functions:<\/p>\n

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

The new script creates a cleaner presentation of the database results.<\/p>\n

 <\/p>\n

Changes to Assemblies list for GUIs<\/h3>\n

Previous versions of PowerShell Studio would list some of the core .NET assemblies in order to provide PrimalSense, and also to ensure the System.Windows.Form<\/em> assembly was loaded when running the GUI script.<\/p>\n

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

PowerShell Studio 2018 will no longer list the base .NET assemblies such as mscorlib<\/em>, system<\/em>, system.data,<\/em> etc.\u00a0 As a result, the assembly list will most likely be empty but PowerShell Studio will continue to provide PrimalSense for these assemblies without explicitly listing them. This way, PowerShell Studio will only list external assemblies that you explicitly specify .<\/p>\n

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

Note: GUI psf files created with previous versions of PowerShell Studio will still retain the old assemblies list. New psf files created in PowerShell Studio 2018 will have an empty list.<\/p>\n

 <\/p>\n

Performance Improvements<\/h2>\n

We made several performance improvements to the debugger and projects.<\/p>\n

 <\/p>\n

Improved Debugger Performance for Large Data Arrays<\/h3>\n

Hovering your cursor over a value with a large array, should now respond much faster than previous versions.<\/p>\n

 <\/p>\n

Improved Performance Handling for Output<\/h3>\n

We made improvements to our output handling to reduce the impact of large amounts of output flooding the UI. The application should now be more responsive in these situations.<\/p>\n

 <\/p>\n

Improved Project Syncing Performance<\/h3>\n

We reduced the time it takes to update a project by making some improvements to the performance of project file syncing.<\/p>\n

<\/h3>\n

 <\/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 are happy to announce the release of PowerShell Studio 2018, which is included as part of the regular update cycle for our subscribers.   New Features and Improvements The 2018 release includes many improvements and new features to enhance your overall experience with PowerShell Studio.   PrimalSense Improvements Updated Cache We updated our cache […]<\/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,624,21,632],"tags":[1233,1016,645,155,141],"class_list":["post-14353","post","type-post","status-publish","format-standard","hentry","category-powershell-studio","category-service-build","category-software-news","category-whats-new-software-news","tag-1233","tag-powershell-studio","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\/14353","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=14353"}],"version-history":[{"count":7,"href":"https:\/\/dev.sapien.com\/blog\/wp-json\/wp\/v2\/posts\/14353\/revisions"}],"predecessor-version":[{"id":14452,"href":"https:\/\/dev.sapien.com\/blog\/wp-json\/wp\/v2\/posts\/14353\/revisions\/14452"}],"wp:attachment":[{"href":"https:\/\/dev.sapien.com\/blog\/wp-json\/wp\/v2\/media?parent=14353"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/dev.sapien.com\/blog\/wp-json\/wp\/v2\/categories?post=14353"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/dev.sapien.com\/blog\/wp-json\/wp\/v2\/tags?post=14353"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}