SAPIEN Technologies

Nah, 1.0 folder doesn't matter to us. I'll have to do some research on this to determine if PrimalScript simply is not even calling PowerShell or if PowerShell gets stuck somewhere.
I'll be back.

I'll check if we can just shell out to signcode.exe which is redistributable I believe. Keep a look on the changelog and post over at our support forum.

PrimalScript uses the Microsoft Script signing control. Unfortunately this is not working with PFX file. You must have your signature in your certificate store. Package the scripts you want to protect with PrimalScript's script packager and specify the "SAPIEN Script Host" option. Your scr...

Under your Windows folder, you should have a folder called:
Microsoft.NETFramework
what sub folders do you have there?

Alex

Hmm. Works fine here, I'll have to look into it if there is anything we can do to determine where it actually gets stuck.
What OS are you running this on?
Can you possible check on another machine?

Alex

It seems there is something wrong about how we pass the pfx file to PowerShell. Leave the field blank and PrimalScript will tell PowerShell to use the first code signing signature in your store.
We'll update the component with the next service build.
Alex

Please let us know what version (with exact build) and edition of PrimalScript you have. We also need to know what version of PowerShell you have installed. Also, to narrow down what it could be, create a simple one line script, something like Write-Host "Hello World" and save it as hello ...

Ah, yes, surpassed by the times. Do you have a version of the MSDN library installed? I mean the actual software?

The SDK help files need to merge with Microsoft's MSDN Library, which uses a new version of Document Explorer. Largely undocumented as that is, I am not sure if that works at this time. Setting it to use MSDN.NET would be the correct setting. Since PrimalScript comes with a full-fledged help for VBS...

Still trying to figure out what could make it do that. Only a hanging PowerShell thread could account for that. And yes you can. Just add PowerShell.exe to the Tools browser and edit the arguments to it so that it launches the currently active file as a script. The macros for that are on the context...