1). Probably we could have an additional custom action that would change ExecutionPolicy to RemoteSigned and at the installation end return the original value.
2). Advanced installer could run scripts with Bypass argument
. Not sure, why it doesn't do that already?
Code: Select all
powershell -ExecutionPolicy Bypass -File script.ps1
3). Convert PowerShell scripts into .NET executable code and just launch exe file in a custom action.
I'm wondering what would be the best practice option in this case?