Hello,
Thank you for your in depth description. Indeed, the easiest way to achieve what you want will be to use the following condition for the "WriteRegistryValues" action.
Now, I think your first attempt to use the above condition in our "Table Editor" page didn't work because of an Advanced Installer limitation. The "AI_DETECTED_MINOR_UPGRADE" property (and also several AI reserved property) won't be evaluated and set as long as you didn't use the property in a field from our UI which is a
smart edit control. So, if you don't use the "AI_DETECTED_MINOR_UPGRADE" property at least in one field which a smart edit control (it is not the case for any fields from our "Table Editor" page), then the "AI_DETECTED_MINOR_UPGRADE" property will be always empty, thus your condition will be always false. We will try to update our help files with this info too.
The solution to this limitation is to also use the "AI_DETECTED_MINOR_UPGRADE" in a condition field which is a smart condition control. For instance you can create a dummy custom launch condition which will use the "AI_DETECTED_MINOR_UPGRADE" property, but will never trigger. Here is what you can do:
1. go to "Launch Conditions" page -> "Custom" tab and add a new launch condition like this:
- Condition: (AI_DETECTED_MINOR_UPGRADE) OR (1=1)
Description: Dummy launch condition used to resolve the AI_DETECTED_MINOR_UPGRADE property. This launch condition will never be triggered.
2. go to "Table Editor" page and select the "InstallExecuteSequence" table
3. add the following condition on the "WriteRegistryValues" action
4. rebuild and test again your minor upgrade setup
Let us know if this helped.
All the best,
Daniel
FOLLOW US
Get the latest news in Application Packaging