{"id":13898,"date":"2017-09-15T06:00:57","date_gmt":"2017-09-15T13:00:57","guid":{"rendered":"https:\/\/www.sapien.com\/blog\/?p=13898"},"modified":"2017-09-14T14:31:54","modified_gmt":"2017-09-14T21:31:54","slug":"using-powershell-core-in-primalscript","status":"publish","type":"post","link":"https:\/\/dev.sapien.com\/blog\/2017\/09\/15\/using-powershell-core-in-primalscript\/","title":{"rendered":"Using PowerShell Core in PrimalScript"},"content":{"rendered":"

Back in May 2016, SAPIEN did a blog post about “Using Bash with PrimalScript 2016<\/a>“.\u00a0 In a way, using similar steps, we can setup and use PowerShell Core in PrimalScript 2017 as well.<\/p>\n

Keep in mind, due to the fact that PowerShell Core still in it’s early stages, you’ll have modify the console executable path each time you install the updated version of PowerShell Core: “C:\\Program Files\\PowerShell\\x.0.0-xxxx-x<\/em><\/strong>“.<\/p>\n

Another thing, PowerShell Core still is progressing in its Beta stage. So, SAPIEN won’t support any issues found with PowerShell Core until it reaches RTM status. If you find any issues with “PowerShell Core”, please send them directly to their Github link at:
\nhttps:\/\/github.com\/PowerShell\/PowerShell<\/a><\/p>\n

 <\/p>\n

The Setup<\/span><\/h3>\n

By default PrimalScript, will execute the PowerShell script(s) under Windows PowerShell. In order allow execution of PowerShell Core scripts, we need to add the PowerShell Core executable in their list of “Command Window<\/strong>“.<\/p>\n

1. From the PrimalScript menu, click on “File<\/strong>“, and scroll-down to “Options<\/strong>“:<\/p>\n

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

2. Go to “File Groups<\/strong>“, to “Add New<\/strong>” PowerShell Core file groups:<\/p>\n

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

3. Go to “Command Window<\/strong>“, to add “New<\/strong>” Shell, and the “Rename<\/strong>” the “New Shell<\/strong>” name to “PowerShell Core 64 bit<\/strong>“:<\/p>\n

\"PrimalScript_PSC_03\"<\/a>
\n\"PrimalScript_PSC_04\"<\/a>
\n\"PrimalScript_PSC_05\"<\/a><\/p>\n

4. After all these changes are done, you’ll be asked to “..restart..”<\/em> PrimalScript.<\/p>\n

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

 <\/p>\n

Executing the code<\/span><\/h3>\n

Before executing the code, you\u2019ll need to open the PowerShell Core console:<\/p>\n

1. From the menu, click on the “View<\/strong>” tab, then click on “Shell<\/strong>“, and under the “Console Window<\/strong>” select “PowerShell Core 64 bit<\/strong>“.<\/p>\n

\"PrimalScript_PSC_08\"<\/a>
\n\"PrimalScript_PSC_07\"<\/a><\/p>\n

Now that the PowerShell Core console is open, anything that you select to execute will go to that active console.<\/p>\n

2. To execute the code, proceed to highlight a portion or the whole script.<\/p>\n

3. Right-click on the highlighted area, and select “Execute selection in PowerShell<\/em><\/strong>“.<\/p>\n

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

4. As this will not complete executing the code, go to the “Console Window<\/strong>“, then press enter at the cursor line to execute the code manually.<\/p>\n

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

 <\/p>\n

Limitations<\/span><\/h3>\n

Remember, PrimalScript will let you create PowerShell Core script(s), but there are few limitation:<\/p>\n

1. Intellisense is meant for Windows PowerShell, so there might be some cmdlet parameters that won’t show.
\n2. Executing selected code block, at the “Command Window<\/strong>“, you’ll need to press enter to run the code.<\/p>\n

The workaround for executing the code automatically, is to execute the following command:
\n“Remove-Module PSReadLine<\/strong><\/span>”<\/p>\n

Now you can create and test your code without any problem.<\/p>\n

Please, feel free to give it a try!<\/p>\n","protected":false},"excerpt":{"rendered":"

Back in May 2016, SAPIEN did a blog post about “Using Bash with PrimalScript 2016“.\u00a0 In a way, using similar steps, we can setup and use PowerShell Core in PrimalScript 2017 as well. Keep in mind, due to the fact that PowerShell Core still in it’s early stages, you’ll have modify the console executable path […]<\/p>\n","protected":false},"author":47,"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":[1143,410],"tags":[1215,1216],"class_list":["post-13898","post","type-post","status-publish","format-standard","hentry","category-powershell","category-primalscript-software-news","tag-powershell-core","tag-primalscript-2017"],"jetpack_featured_media_url":"","_links":{"self":[{"href":"https:\/\/dev.sapien.com\/blog\/wp-json\/wp\/v2\/posts\/13898","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\/47"}],"replies":[{"embeddable":true,"href":"https:\/\/dev.sapien.com\/blog\/wp-json\/wp\/v2\/comments?post=13898"}],"version-history":[{"count":5,"href":"https:\/\/dev.sapien.com\/blog\/wp-json\/wp\/v2\/posts\/13898\/revisions"}],"predecessor-version":[{"id":13923,"href":"https:\/\/dev.sapien.com\/blog\/wp-json\/wp\/v2\/posts\/13898\/revisions\/13923"}],"wp:attachment":[{"href":"https:\/\/dev.sapien.com\/blog\/wp-json\/wp\/v2\/media?parent=13898"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/dev.sapien.com\/blog\/wp-json\/wp\/v2\/categories?post=13898"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/dev.sapien.com\/blog\/wp-json\/wp\/v2\/tags?post=13898"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}