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
- :
- Disable feature (but do not hide it)
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 11, 2008
04:13 AM
Disable feature (but do not hide it)
the following problem is from other web site:
I have a number of features in my installation project, and some of
them have prerequisites that must be checked (ie. IIS must be
installed, Office must be installed, ...).
Right now I'm using a 'Condition' tag on the Feature that sets the
Level to '0' if the condition isn't met, however this completely hides
the feature. Is it possible to disable (grayed out) the feature
instead of hiding it? I think that this will be easier for our
users...
Thanks.
I have a number of features in my installation project, and some of
them have prerequisites that must be checked (ie. IIS must be
installed, Office must be installed, ...).
Right now I'm using a 'Condition' tag on the Feature that sets the
Level to '0' if the condition isn't met, however this completely hides
the feature. Is it possible to disable (grayed out) the feature
instead of hiding it? I think that this will be easier for our
users...
Thanks.
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Mar 11, 2008
10:13 AM
There's no way to disable a feature, still have it displayed, and prevent the user from changing it's state in an MSI project. The feature can be hidden by setting its install level to 0, or it can be deselected and visible by setting its install level to a value greater than the value of the INSTALLLEVEL property (the feature can still be selected by the user if they click on it in the CustomSetup dialog). To prevent the user from installing the feature if it is visible and its conditions for install have not been met, a custom action could be used to validate the feature state.