Setting ExecutionPolicy when building a script
Posted: Thu Sep 01, 2016 10:34 pm
Product, version and build: PrimalScript 2016 version 7.2.92
32 or 64 bit version of product:
Operating system: Win7
32 or 64 bit OS: 64
Hi
I have written a bunch of stuff which seems to work fine. This is just manipulating data in csv files.
I have built the script into an EXE file which also works fine for me on my system.
When my client runs it it fails. She has a Win7 x32 bit setup. I have the Platform set at "Local Machine 32 Bit"
I suspect it has something to do with the execution policy of the machine as she can run it via a .cmd fine with command line [c:\windows\...powershell.exe -ExecutionPolicy Bypass <filepath and name>.ps1]
Is there a way to set that execution policy in the build so that the script content is not exposed?
Thanks
Wayne
32 or 64 bit version of product:
Operating system: Win7
32 or 64 bit OS: 64
Hi
I have written a bunch of stuff which seems to work fine. This is just manipulating data in csv files.
I have built the script into an EXE file which also works fine for me on my system.
When my client runs it it fails. She has a Win7 x32 bit setup. I have the Platform set at "Local Machine 32 Bit"
I suspect it has something to do with the execution policy of the machine as she can run it via a .cmd fine with command line [c:\windows\...powershell.exe -ExecutionPolicy Bypass <filepath and name>.ps1]
Is there a way to set that execution policy in the build so that the script content is not exposed?
Thanks
Wayne