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
- :
- Re: Feature Level conditions problems
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
‎Oct 03, 2012
08:47 AM
Feature Level conditions problems
I have a basic MSI project that includes the Setup Type dialog. I have set the property for the radio button group to AC_SETUPTYPE in this dialog.
I have three setup types. MAIN, WORKGROUP, MOBILE
I have two features that have feature conditions set on them
Level:0, AC_SETUPTYPE ~= "WORKSTATION"
Level:1, AC_SETUPTYPE ~="MAIN" OR AC_SETUPTYPE ~= "MOBILE"
However, during install these features are installed no matter what the value of AC_SETUPTYPE is set to, these features are always set to ADDLOCAL.
What am I missing to get my desired affect of not installing the features if the setup type is "WORKSTATION"?
Do I need to set INSTALLEVEL?
Thanks.
I have three setup types. MAIN, WORKGROUP, MOBILE
I have two features that have feature conditions set on them
Level:0, AC_SETUPTYPE ~= "WORKSTATION"
Level:1, AC_SETUPTYPE ~="MAIN" OR AC_SETUPTYPE ~= "MOBILE"
However, during install these features are installed no matter what the value of AC_SETUPTYPE is set to, these features are always set to ADDLOCAL.
What am I missing to get my desired affect of not installing the features if the setup type is "WORKSTATION"?
Do I need to set INSTALLEVEL?
Thanks.
(2) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Oct 03, 2012
10:28 AM
You have a race condition. The Condition table gets evaluated during the costing process and your radio dialog is occuring after words.
This might help you:
http://kb.flexerasoftware.com/selfservice/viewContent.do?externalID=Q103232
This might help you:
http://kb.flexerasoftware.com/selfservice/viewContent.do?externalID=Q103232
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Oct 03, 2012
12:50 PM
Chris,
Thanks for the response. I found my error. I had a brain lapse and was placing my code events in the radio button group and not the NEXT button, so no feature changes were taking place.
I have done this I cannot think of how many times and I don't know why I had a lapse this time around *grin*. All I know is that all of a sudden is that light dawned on me and I realized that a radio button group really does not respond to 'events' just buttons and checkbox states.
Now to test the changes from a command line ... which is why I implemented the feature conditions to allow setting properties from the command line.
Thanks for the response. I found my error. I had a brain lapse and was placing my code events in the radio button group and not the NEXT button, so no feature changes were taking place.
I have done this I cannot think of how many times and I don't know why I had a lapse this time around *grin*. All I know is that all of a sudden is that light dawned on me and I realized that a radio button group really does not respond to 'events' just buttons and checkbox states.
Now to test the changes from a command line ... which is why I implemented the feature conditions to allow setting properties from the command line.
![](/skins/images/A5EADE085F77DE82FB3B14D6B307AE6A/responsive_peak/images/icon_anonymous_message.png)