/build/static/layout/Breadcrumb_cap_w.png

Feature condition syntax

Hi,

What's the syntax for wanting a particular Feature to install based on either meeting the criteria of file system search or not existing at all?

Based on a file system search, I'm creating a property called PROJ1 and created a Feature to install a file called abc.cfg based on whether a prerequisite file exists within a certain version range.

Currently, the syntax i have in the conditions is just the name of the property PROJ1. It works fine... but I also want the Feature to install even if the prerequisite does not exist.

appreciate any help.

Thanks,
Rich

0 Comments   [ + ] Show comments

Answers (8)

Posted by: bheers 18 years ago
Second Degree Blue Belt
0
You want to install it even if the condition is satisfied or not so why are you putting a condition to it ?
Posted by: RichR 18 years ago
Senior Yellow Belt
0
I need to have a condition on this Feature, because I have other Features that install same file with different versions.
Posted by: karanp 18 years ago
Senior Yellow Belt
0
Hi RichR,
No need to put the condition if you want the file to be installed in both the case.If not so then please come again with your quey in detail.
Posted by: wiseapp 18 years ago
Second Degree Green Belt
0
Hi Rich:

As karanp said in case you require the file to be installed in both the cases then you dont need a condition however you can by default select the feature. In case you want to put a condition on the basis of system search you could do the same. Even I do not find any need of putting a condition.
Posted by: RichR 18 years ago
Senior Yellow Belt
0
sorry for my lack of detail.... I'll try to better describe what i'm doing...

I have an application that installs a file called abc.cfg and which has two versions of it. One version is to be installed if my system search detects MS Project 2000 and the other version of the file is to be installed if it finds MS Project 2002/2003 OR finds no MS Project installed at all.

I created two system searches that look for winproj.exe... one that searches for versions less than 10.0 and the other for versions higher than 10.0... and respectively, the searches create properties PROJ2000 and PROJ2002.

Aside from my Complete Feature, I created 2 Features... one called CFG2000 and the other called CFG2002... I assigned the respecitive versions of the cfg file accordingly and set the conditon of Feature CFG2000 to PROJ2000 and set the condition of CFG2002 to PROJ2002.

Now, the above works and installs its corresponding Feature based on what version of MS Project is found... but I dont' know the syntax to make Feature CFG2002 install if MS Project 2002/2003 is found or no MS Project at all.

Thanks,
Rich
Posted by: wiseapp 18 years ago
Second Degree Green Belt
0
Hi Rich:

I think this is what you are trying to say:

You want to install the CFG2002 feature irrespective of MS project is found or not ?

In this case you as I said earlier remove the condition from the feature CFG2002 in this case it will install in either of the cases found or not found.

I hope this would answer your query, in case any problems revert.
Posted by: RichR 18 years ago
Senior Yellow Belt
0
Sorry Bhupesh, but that's not correct. I want to install Feature CFG2002 if MS Project 2002 or 2003 is found or if there is no MS Project installed. The other Feature named CFG2000 will install if MS Project 2000 is found.
Posted by: wiseapp 18 years ago
Second Degree Green Belt
0
Alright Rich I got it let me find a way thru scripts that will install your feature as per your requirement.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ