This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Feature Condition Max Length
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Feb 24, 2009
02:16 PM
Feature Condition Max Length
I am trying to add a feature condition to a basic MSI project. The condition is fairly long. There seems to be a limit on the length of the condition string, because when it gets to a certain length (not sure what it is), I get an error "An Invalid condition statement was supplied"
Here is the feature condition:
InstallLevel=1
Condition=
(AMI_VERSION<<"1.9" OR AGILIS_CORE_VERSION<<"2.0.0.18" OR AGILIS_CORE_VERSION<<"2.0.1.6" OR AGILIS_CORE_VERSION<<"2.0.2.6" OR AGILIS_CORE_VERSION<<"2.0.3.12" OR AGILIS_CORE_VERSION<<"2.0.4.1" OR AGILIS_CORE_VERSION<<"2.1.0.11") AND AGILIS_XFS_OPTEVA_VERSION<<"1"
Is there some max limit to the length of a condition? If so, is there a workaround?
Here is the feature condition:
InstallLevel=1
Condition=
(AMI_VERSION<<"1.9" OR AGILIS_CORE_VERSION<<"2.0.0.18" OR AGILIS_CORE_VERSION<<"2.0.1.6" OR AGILIS_CORE_VERSION<<"2.0.2.6" OR AGILIS_CORE_VERSION<<"2.0.3.12" OR AGILIS_CORE_VERSION<<"2.0.4.1" OR AGILIS_CORE_VERSION<<"2.1.0.11") AND AGILIS_XFS_OPTEVA_VERSION<<"1"
Is there some max limit to the length of a condition? If so, is there a workaround?
(4) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Feb 24, 2009
02:30 PM
Viewing the Condition table in the Direct Editor view, it appears the maximum feature condition length is 255 characters. To squeeze a few more characters in, is it an option to use shorter property names?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Feb 24, 2009
02:35 PM
I could shorten the property names, but then I would have to go back and do that for all my other features that use these properties. A lot of extra work that I would like to avoid if possible.
I was thinking about using multiple conditions for the feature but i was not sure if that would work or not. I don't quite understand how feature conditions work when more than one condition is specified.
I was thinking about using multiple conditions for the feature but i was not sure if that would work or not. I don't quite understand how feature conditions work when more than one condition is specified.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Feb 24, 2009
06:34 PM
How are you setting the AGILIS_CORE_VERSION property? Do you want just those specific versions, or any version less than a particular one? Before sorting out how multiple feature conditions work out, perhaps that part can be condensed...
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Feb 25, 2009
08:14 AM
I needed specific versions, so a range check was not possible.
For now, I bit the bullet and reduced the length of all the properties so that I could get it to work.
I guess the only thing I was not sure of is how multiple feature conditions are handled. Are they mutually exclusive or not?
i.e., If I have two conditions that set the same level for a feature, are they evaluated independantly? If so, what order are they evaluated?
For now, I bit the bullet and reduced the length of all the properties so that I could get it to work.
I guess the only thing I was not sure of is how multiple feature conditions are handled. Are they mutually exclusive or not?
i.e., If I have two conditions that set the same level for a feature, are they evaluated independantly? If so, what order are they evaluated?