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: Set Feature Install Level and CustomSetup
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
Mar 25, 2010
11:14 AM
Set Feature Install Level and CustomSetup
Basic MSI project with a handful of features. I created a custom dialog to allow the user to enter a license key. The key is validated on the click of the Next button which is tied to a Custom Action event. This custom action parses the key and sets a public property (for each feature) based on whether that feature should be installed.
Example:
FeatureA has 2 conditions:
Level = 0 FEATUREA_INSTALL=N
Level = 100 FEATUREA_INSTALL=Y
I have set up each feature with similar conditions using separate properties.
I want the end result to be that FeatureA is not displayed in the CustomSetup dialog if a certain part of the key says it shouldn't.
In the log I can see:
PROPERTY CHANGE: Adding FEATUREA_INSTALL property. Its value is 'N'.
But when I click to the CustomSetup dialog, it is still shown.
What am i missing?
Example:
FeatureA has 2 conditions:
Level = 0 FEATUREA_INSTALL=N
Level = 100 FEATUREA_INSTALL=Y
I have set up each feature with similar conditions using separate properties.
I want the end result to be that FeatureA is not displayed in the CustomSetup dialog if a certain part of the key says it shouldn't.
In the log I can see:
PROPERTY CHANGE: Adding FEATUREA_INSTALL property. Its value is 'N'.
But when I click to the CustomSetup dialog, it is still shown.
What am i missing?
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Mar 26, 2010
05:05 PM
I think it's that Windows Installer evaluates those conditions when CostFinalize runs, which is normally before any dialog boxes are displayed.
If you need to do this, common practice seems to be to modify the in-memory MSI database; searching these forums for "hide feature at runtime" will turn up some examples in different languages.
If you need to do this, common practice seems to be to modify the in-memory MSI database; searching these forums for "hide feature at runtime" will turn up some examples in different languages.