Use native engine in package scripts?

[mupdike]

Product, version and build: Primalscript 7.2.82
32 or 64 bit version of product: x64
Operating system: Win 8.1 x64
32 or 64 bit OS:

I am using the script packager for the first time and wanted to know if there's a way for my powershell script to be setup to use the target systems powershell engine based on the default architecture? So the exe will only call the powershell.exe on the machine and pass my .ps1 to it for execution.

Thanks for any help/advice.
Mike

DO NOT POST SUBSCRIPTIONS, KEYS OR ANY OTHER LICENSING INFORMATION IN THIS FORUM

[Alexander Riedel]

Yes. Choose the "Microsoft Windows Powershell (Command line)" engine fitting your platform (x64 or Win32)
It will create a temporary file during execution though. Just so you are aware.
FYI, the SAPIEN PowerShell host engines also use the "native" powershell engine. They just do not use temporary files or powershell.exe

[mupdike]

In the Engine Type pull down it looks like I have to specifically select either the Win32 or x64 engine. I don't see a 'native' choice so that it would just use the engine for the architecture that the command is being run on. For an example if I write a .cmd file that says powershell.exe -command .\test.ps1 this will use the correct bitness powershell based on the architecture of the machine. I'm looking to replicate that in a more properly wrapped exe, if possible.

Thanks for the help!
Mike

[Alexander Riedel]

Yeah, I guess that could be done. It would have to always be a 32 bit process.
I'll see what we can cook up.

[Alexander Riedel]

Add the engine in the attached zip file to your installation and see if that does what you want.

[mupdike]

Thanks for the exe, just getting that is incredible support. In attempting to test this I am getting an error of: 'Cannot run Script, error: The system cannot find the file specified. (image attached) Is this something I'm doing wrong? The .ps1 is in the same directory as the exe and the files the ps1 need (App-V related files).

[Alexander Riedel]

umm. Ok, let me check.

[Alexander Riedel]

Ok, try this one.
You do not need to deploy the script file with the exe, it is packaged inside.

[mupdike]

This worked perfectly! It imported the App-V Powershell cmdlet in the proper architecture on both x86 and AMD64 machines. Thank you very much for the assistance!

[Alexander Riedel]

Glad to hear it. This will be part of the next service build.