What is the problem or limitation you are having?
MSI installers can be executed in "unattended" or "quiet" mode, which means the user won't be present to interact with the installer (the equivalent of a --noinput run for Briefcase).
If an MSI has a post-install script, the script needs to know if the installer is running in unattended mode so that the script can avoid presenting questions to the user and assume appropriate defaults.
Describe the solution you'd like
Post-install and pre-uninstall scripts should have access to a INSTALLER_UNATTENDED environment variable that is set to 1 if the MSI is running "quiet" mode.
Describe alternatives you've considered
Additional context
A "Quiet mode" install can be triggered with:
msiexec /i MyInstaller.msi /qn
Initial research suggests that <Condition>UILevel < 3</Condition> can be used to identify "quiet mode" in the installer as part of a conditional property definition.
What is the problem or limitation you are having?
MSI installers can be executed in "unattended" or "quiet" mode, which means the user won't be present to interact with the installer (the equivalent of a
--noinputrun for Briefcase).If an MSI has a post-install script, the script needs to know if the installer is running in unattended mode so that the script can avoid presenting questions to the user and assume appropriate defaults.
Describe the solution you'd like
Post-install and pre-uninstall scripts should have access to a
INSTALLER_UNATTENDEDenvironment variable that is set to 1 if the MSI is running "quiet" mode.Describe alternatives you've considered
Additional context
A "Quiet mode" install can be triggered with:
Initial research suggests that
<Condition>UILevel < 3</Condition>can be used to identify "quiet mode" in the installer as part of a conditional property definition.