Launch condition based on property using system search fails. It seems that the property does not get set at runtime. is there a way to force the property to be set at runtime so the launch condition gets the correct value? the property is based on a registry value.
0 Comments   [ - ] Hide Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity



If you want the property to get set at runtime, you need to set your custom action in the execute immediate sequence after the appsearch and to see the property in the dialog version, place it at the same position at the User Interface.
hope this helps[8|]

Stefan V
Answered 08/10/2004 by: StevieMcR
Senior Yellow Belt

Please log in to comment
Is a Launch Condition the same as a custom action? I'm trying to set a Launch Condition.
The launch condition states "NOT PREVIOUSFILE". The "PREVIOUSFILE" property is the result of a system search for the existance of a file on the destination machine. the problem seems to be that the launch condition checks the value of the property before the appsearch action runs.
Answered 08/10/2004 by: mikef
Yellow Belt

Please log in to comment
I think it will because launch conditions run before anything really. I think you'll have to make a custom action that quits the install based on the condition.
Answered 08/10/2004 by: kkaminsk
Ninth Degree Black Belt

Please log in to comment