From the menu, click on the “ View” tab, then click on “ Shell“, and under the “ Console Window” select “ PowerShell Core 64 bit“. After all these changes are done, you’ll be asked to “.restart.” PrimalScript.īefore executing the code, you’ll need to open the PowerShell Core console:ġ. Go to “ Command Window“, to add “ New” Shell, and the “ Rename” the “ New Shell” name to “ PowerShell Core 64 bit“:Ĥ. Go to “ File Groups“, to “ Add New” PowerShell Core file groups:ģ. From the PrimalScript menu, click on “ File“, and scroll-down to “ Options“:Ģ. In order allow execution of PowerShell Core scripts, we need to add the PowerShell Core executable in their list of “ Command Window“.ġ. If you find any issues with “PowerShell Core”, please send them directly to their Github link at:īy default PrimalScript, will execute the PowerShell script(s) under Windows PowerShell. So, SAPIEN won’t support any issues found with PowerShell Core until it reaches RTM status.
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“.Īnother thing, PowerShell Core still is progressing in its Beta stage. In a way, using similar steps, we can setup and use PowerShell Core in PrimalScript 2017 as well.
Back in May 2016, SAPIEN did a blog post about “ Using Bash with PrimalScript 2016“.
0 kommentar(er)
