Hi David,
First of all I apologize I misunderstood your specific scenario.
In order to achieve that you can go in the “Search” page and use a custom search, where the object of your search can be either a component, registry key, folder, a file etc.
In order to search for a registry entrance you can go in the
“Search” page and use the [New Search Wizard] toolbar button and follow step-by-step wizard directions.
The result of your search will be stored in a
public property(e.g.
REG1_PATH ).
Add a another registry search (e.g.
REG2_PATH ) for the second search location.
Then you can go in the “Custom Actions” page and add two
“Set installer property” predefined custom actions with sequence.
For the first custom action you can edit its properties like:
Property – field:
FINAL_PATH this property will further serve to the launch condition
Value – field:
[REG1_PATH] the value of the first registry search
Condition – field:
REG1_PATH it will be only executed if there was found in the first registry location
For the second custom action you can edit its properties like:
Property – field:
FINAL_PATH this property will further serve to the launch condition
Value – field:
[REG2_PATH] the value of the second registry search
Condition – field:
( NOT REG1_PATH ) AND REG2_PATH it will only be executed if was nothing found in the first registry location and there was found in the the second registry location
Also you should add these two custom actions in the “Wizard Dialogs Stage” after the "Searches" stage using a “drag-and-drop” operation while the “SHIFT” key is pressed.
You can go now in the “Launch Conditions” page and create a
launch condition.
In the “Condition” field you can type
FINAL_PATH and in the “Description” field you can have a custom message(e.g. “Prerequisite software was not found!”).
Please let us know if that helped otherwise give us more details.
Best regards,
Dan
FOLLOW US
Get the latest news in Application Packaging