{"id":7129,"date":"2014-04-10T09:00:06","date_gmt":"2014-04-10T17:00:06","guid":{"rendered":"http:\/\/www.sapien.com\/blog\/?p=7129"},"modified":"2014-04-10T09:26:26","modified_gmt":"2014-04-10T17:26:26","slug":"powershell-studio-2014-what-new-in-the-editor","status":"publish","type":"post","link":"https:\/\/dev.sapien.com\/blog\/2014\/04\/10\/powershell-studio-2014-what-new-in-the-editor\/","title":{"rendered":"PowerShell Studio 2014: What New in the Editor?"},"content":{"rendered":"

Let\u2019s look at some of the new features you will find in PowerShell Studio 2014\u2019s editor.<\/p>\n

Improved Syntax Coloring<\/strong><\/p>\n

One of the first editing features you might have noticed in PowerShell Studio 2014 is the improved syntax coloring.<\/p>\n

Parameter Attributes and Type Coloring:<\/em><\/p>\n

PowerShell Studio will now color parameter attributes and types when valid:<\/p>\n

\"Attribute<\/p>\n

External Tools Coloring:<\/em><\/p>\n

Do you use tools like ping or ipconfig? Well we now color those tools as well:<\/p>\n

\"External<\/p>\n

Unknown Command Coloring:<\/em><\/p>\n

When the editor is unable to determine what a command is, it will color it as an unknown command. This gives you a visual hint that something maybe be incorrect in the script. For example, if you mistype Get-Process, the commands will display as follows:<\/p>\n

\"Unknown<\/p>\n

DSC Coloring:<\/em><\/p>\n

We provide syntax coloring for DSC scripts:<\/p>\n

\"Configuration\"<\/p>\n

And yes, configurations will appear in the Function Explorer:<\/p>\n

\"Configuration<\/p>\n

As time progresses, we will be adding more support for DSC.<\/p>\n

 <\/p>\n

Improved PrimalSense Support<\/strong><\/p>\n

We have also made numerous improvements to PowerShell Studio 2014\u2019s PrimalSense.<\/p>\n

Parameter Attribute PrimalSense:<\/p>\n

\"Parameter<\/p>\n

Parameter Alias for Functions:<\/em><\/p>\n

PowerShell Studio will now display parameter alias for user defined functions:<\/p>\n

\"Function<\/p>\n

 <\/p>\n

ValidateSet PrimalSense:<\/em>
\nPowerShell Studio even provides ValidateSet PrimalSense for user defined functions:<\/p>\n

\"Validate<\/p>\n

\u00a0<\/em><\/p>\n

New-Object Properties<\/em><\/p>\n

You can use the New-Object cmdlet\u2019s Properties<\/em> parameter to specify the initial values for the object\u2019s properties using a hash table. PowerShell Studio 2014 makes this easier by providing you with the list of the object type\u2019s properties when working within a hash table:<\/p>\n

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


\nDot Sourcing<\/strong><\/em><\/p>\n

We also provide PrimalSense support for dot sourced files, including parameter completion:<\/p>\n

\"Dot<\/p>\n

 <\/p>\n

PowerShell Studio now provides syntax coloring for functions in dot sourced files:<\/p>\n

\"Dot<\/p>\n

Use the editor\u2019s context menu to open the dot sourced file:<\/p>\n

\"Go<\/p>\n

 <\/p>\n

Block Editing<\/strong><\/p>\n

Edit multiple lines at once by pressing\u00a0 (Alt + Shift + Up \/Down):<\/p>\n

\"Multiline<\/p>\n

The editor also includes various other improvements, including PrimalSense support for PowerShell variables, such as $Error and $_ in the try catch block.<\/p>\n","protected":false},"excerpt":{"rendered":"

Let\u2019s look at some of the new features you will find in PowerShell Studio 2014\u2019s editor. Improved Syntax Coloring One of the first editing features you might have noticed in PowerShell Studio 2014 is the improved syntax coloring. Parameter Attributes and Type Coloring: PowerShell Studio will now color parameter attributes and types when valid: External […]<\/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,632,25],"tags":[734,874,141],"class_list":["post-7129","post","type-post","status-publish","format-standard","hentry","category-powershell-studio","category-whats-new-software-news","category-windows-powershell","tag-editor","tag-powershell-studio-2014","tag-whats-new"],"jetpack_featured_media_url":"","_links":{"self":[{"href":"https:\/\/dev.sapien.com\/blog\/wp-json\/wp\/v2\/posts\/7129","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=7129"}],"version-history":[{"count":5,"href":"https:\/\/dev.sapien.com\/blog\/wp-json\/wp\/v2\/posts\/7129\/revisions"}],"predecessor-version":[{"id":7176,"href":"https:\/\/dev.sapien.com\/blog\/wp-json\/wp\/v2\/posts\/7129\/revisions\/7176"}],"wp:attachment":[{"href":"https:\/\/dev.sapien.com\/blog\/wp-json\/wp\/v2\/media?parent=7129"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/dev.sapien.com\/blog\/wp-json\/wp\/v2\/categories?post=7129"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/dev.sapien.com\/blog\/wp-json\/wp\/v2\/tags?post=7129"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}