Perhaps - for the future - AI could add a new PowerShell-based CA that implements your suggestion of using the -Command?
Basically, an inline script that is launched not via dot-source, but using your proposed workaround.
The inline scripts are used mostly to set various internal properties. So, invoking the external scripts via powershell.exe may not work well, I suspect.
Looks like I will need to convert them all to 'native' CAs invoked from a DLL. Thanks, .a
Our installer is using inline PS scripts (and at one point an external PS script). Reports started coming in about installer failure. The reason turned out to be tightly locked-down environments where the PowerShell is running in the Restricted or Constrained language mode.
thanks for the reply and sorry about a delayed response.
I didn't mean the UAC, but rather the installer dialog changing into the one showing the VC++ redistributable with the checkmark prompting to install it.
Fortunately, as I started working on creating a reproducible .aip, I ...
before I describe the issue, I have to state that I am of sound mind and don't believe in miracles.
Now, I am seeing a really strange issue. We have a PowerShell script that is executed via the 'run powershell script file' custom action. In the script, a few properties are read and set. I ...
I have recently added installation of the VC++ redistributables to our installer. I have specified the /q /norestart to all 3 types if installation (on the 'Installation' page). I expected that the installation would always be silent. Alas, when running with the full UI, there is the prompt ...
The issue mentioned in the thread you linked is exactly what I see. Our Jenkins agents are hosted in Azure. Maybe there is some strange interaction.
I agree, this is something that MSFT should ultimately fix. Meanwhile - workarounds
We recently switched to the AAS for our signing needs. A part of signing is done by our build scripts using signtool.exe. Another part is performed by Advanced installer.
One thing I noticed with AAS is that on occasion, signtool.exe will simply hang. It will never exit (I've not tried ...
I do use the 'attached script' in some places and 'inline PS script' in other places. The thing is that the inline PS script sources the temporary file via the dot operator.
$script = $param
. $script # some PS code before calling a function from the temporary PS script file ...
Started the installer, found the .ps1 file extracted into the temp folder. Opened it - it's signed. Modified the file, including deleting a part of the signature block. Proceeded with the installation. It went without a hitch.
I suppose the reason for that is that this temp ...
FOLLOW US
Get the latest news in Application Packaging