Thu May 09, 2013 10:09 am
Hello,
You can skip doing your own custom action because a new search doesn't use the result of another search, but you will have to add several custom actions “Set installer property”. Add 3 custom actions “Set installer property” that will set the higher version. All these three custom actions will set the same “Property” field to a value that will hold your maximum version, let's say ( MAX ). Also, for every custom action you will have to uncheck the “Uninstall” and “Maintenance” options.
The first custom action will have the “Value” of your first search name(e.g. [VERSION_17]) and the “Condition” field set to, in our example “VERSION_17”.
The second custom action will have the “Value” of your second search name (e.g. [VERSION_16] ) and the “Condition” field set to, in our example “VERSION_16 AND NOT VERSION_17”.
The third custom action will have the “Value” of your third search name (e.g. [VERSION_15] ) and the “Condition”, in our example “VERSION_15 AND NOT VERSION_16 AND NOT VERSION_17”.
This 3 custom actions were for the higher value. Now we need another 3 custom actions for the minimum version.
Add another 3 custom actions “Set installer property”, for each of them you will set the “Property” field to a value that will hold your minimum version, let's say (MIN). Also, for every custom actions you will have to uncheck the “Uninstall” and “Maintenance” options.
Do the same thing as before but for minimum version. Now all you have to do is to reverse conditions from precedent three searches for the maximum version.
Please note that all custom action must be placed in “Wizard Dialogs Stage” after the “Searches”.
Here you have a sample. I used two “Edit Box” controls to display the MIN and MAX. To to this, I set the “Property Name” of each edit box to MAX and MIN because these are the properties that hold my maximum version and my minimum version.
Best regards,
Dan
- Attachments
-
- SearchRegistryKey.aip
- (12.66KiB)Downloaded 365 times