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: Disable feature if NOT IE7FOUND
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
‎Nov 12, 2008
05:45 PM
Disable feature if NOT IE7FOUND
(4) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Nov 12, 2008
05:50 PM
You can use a Feature condition ( Condition table ) to set the install level to 0. This will disable and hide the feature.
But care must be excericsed in considering what this means in repair/upgrade/reinstall/modify ectera if IE7FOUND becomes true.
But care must be excericsed in considering what this means in repair/upgrade/reinstall/modify ectera if IE7FOUND becomes true.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Nov 12, 2008
06:03 PM
Thanks, that is not quite the effect that I want, I want the user still to have an option to install the feature but change the default to not install.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Nov 12, 2008
06:07 PM
Sorry, you said disable not un-select.
It's the same pattern, but now set the feature to have an install level of greater then that of the InstallLevel property ( typically 100 by default so set it to 101+ )
The user can still manually select it so either hide away the custom setup dialog or put a blocking custom action on the Next Button that disallows the feature to be selected if you so choose.
BTW, along the lines of 'too much choice is bad' paradox... whats the point of not installing this feature if IE7 isn't installed but you can still optionally install it?
It's the same pattern, but now set the feature to have an install level of greater then that of the InstallLevel property ( typically 100 by default so set it to 101+ )
The user can still manually select it so either hide away the custom setup dialog or put a blocking custom action on the Next Button that disallows the feature to be selected if you so choose.
BTW, along the lines of 'too much choice is bad' paradox... whats the point of not installing this feature if IE7 isn't installed but you can still optionally install it?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Nov 12, 2008
06:17 PM
Thanks - go it.