While PrimalScript has had the ability to run scripts in a PowerShell 6 or 7 console for some time, support for new language elements, packaging, etc. was not implemented. Now that PowerShell 7 has been released, this version adds full support, across the board.
PrimalScript 2020 can now run PowerShell scripts with the new PowerShell 7 engine the way you are used to. Simply run your script, and the output appears in the output panel.
Debugging PowerShell 7 scripts works just the same way as debugging with Windows PowerShell.
It is easier than ever to switch between the PowerShell version you want to use; Windows PowerShell or PowerShell 7 using .NET Core 3.1. You can edit, debug, run, and test without having to change the tool.
Packaging for PowerShell 7 is also supported. At this time, there are options for Windows and console applications. Support for other packager targets will be added soon.
The freshly minted SAPIEN Script Explorer also has the option to run scripts with Windows PowerShell or PowerShell 7.
The PowerShell Cache Editor - the tool controlling which modules and what version you get PrimalSense for - also supports the new PowerShell 7 cache, which is now automatically built after installing PrimalScript 2020. If you install PowerShell 7 after this PrimalScript build (7.7.139) , you will need to run the Cache Builder again.