Problem with Launch conditions
Hello,
I've been trying for a few days now, I've looked at dozens of sites for this and found nothing of real interest.
Here's what I'm trying to do.
I want to check if a specific version a a software is installed before I install another package. Here's what I believed I had to do...
1 - Create a System Search for a specific file or registry value that identifies my first software. (done and tested... a new PROPERTY is created and can be displayed in a msgbox.
2 - Move the AppSearch Action above the LaunchConditions actions (in Gui and Immediate).
3 - Add a launch condition for the product. The problem is here... I cannot see the PROPERTY that I created in the builder... I also tried using [PROPERTY] and PROPERTY for my test but the syntax doesn't check with either...
What am I doing wrong and what should I do to have it work?
Thanks in advance
I've been trying for a few days now, I've looked at dozens of sites for this and found nothing of real interest.
Here's what I'm trying to do.
I want to check if a specific version a a software is installed before I install another package. Here's what I believed I had to do...
1 - Create a System Search for a specific file or registry value that identifies my first software. (done and tested... a new PROPERTY is created and can be displayed in a msgbox.
2 - Move the AppSearch Action above the LaunchConditions actions (in Gui and Immediate).
3 - Add a launch condition for the product. The problem is here... I cannot see the PROPERTY that I created in the builder... I also tried using [PROPERTY] and PROPERTY for my test but the syntax doesn't check with either...
What am I doing wrong and what should I do to have it work?
Thanks in advance
0 Comments
[ + ] Show comments
Answers (4)
Please log in to answer
Posted by:
AngelD
15 years ago
The property will not be added to the Property table while you specify it from the AppSearch and you should not add it either.
The launch condition must resolve to true for the installation to proceed.
If you want the installation to proceed if the file isn't found the you specify NOT YOUR_PROPERTY as the condition.
File must exist for installation to proceed you just skip the NOT.
The launch condition must resolve to true for the installation to proceed.
If you want the installation to proceed if the file isn't found the you specify NOT YOUR_PROPERTY as the condition.
File must exist for installation to proceed you just skip the NOT.
Posted by:
bkelly
15 years ago
Posted by:
jmcfadyen
15 years ago
If the other application is an MSI I would use the upgrade table.
The upgrade table is more precise way of identifying an application and does not "need" to remove the other application. It can be used solely to show existance by messing with the attribute column.
Don't quote me but I think from memory its like 256 or something like that. (I could well be wrong as I am too lazy to check the SDK) but im sure you get the idea.
The upgrade table is more precise way of identifying an application and does not "need" to remove the other application. It can be used solely to show existance by messing with the attribute column.
Don't quote me but I think from memory its like 256 or something like that. (I could well be wrong as I am too lazy to check the SDK) but im sure you get the idea.
Posted by:
AMaltais
15 years ago
Thank you everyone. Your help was really appreciated and with it I was able to fathom how to have it work.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.