Hi,
I have a patch that needs to run both with a user interface and also silently. The problem is that when I run it silently or with a Basic UI, the AI_PATCH property is not set even though it is set to 1 when run with the full user interface. The AI_PATCH property is used to control the execution of custom actions and these custom actions are failing to run during silent and Basic UI installs. The log file shows that AI_PATCH is not set and AI_SET_PATCH is not called during a silent or Basic UI (/qb) install.
The cause of this behaviour appears to be that the action AI_SET_PATCH exists in the InstallUISequence table but does not exist in the InstallExecuteSeqence table.
Would you agree that to set AI_PATCH for silent or Basic UI patch installs, AI_SET_PATCH should be authored into the InstallExecuteSeqence table ? If so, can I use the Advanced Installer user interface to make this change, or do I need to edit the InstallExecuteSeqence table directly ?
Related to this, the action AI_SET_INSTALL is in the InstallUISequence table but not in the InstallExecuteSeqence table, should AI_SET_INSTALL have an entry in the InstallExecuteSeqence to handle silent installs ?
Thanks,
Alastair McDonald
FOLLOW US
Get the latest news in Application Packaging