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 prerequisites in silent install
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 30, 2012
08:13 AM
Feature prerequisites in silent install
Hi!
We have a basic msi project with two features. The two features have opposite conditions so they can't be automatically selected.
Feature A - set level 200 when cA OR cB OR cC
Feature B - set level 200 when NOT(cA or cB or cC)
Both features have feature prerequisites.
We are experiencing when we try to install the setup file silently with /s /v" /qn" on machines that only qualify for feature B, the prereqs for Feature A get installed. When the same setup is installed using non-silent approach the correct prerequisites are installed. If we use /debuglog when running the setup file, we observe that InstallShield tries to install the prereqs before running the installer, and it says: "Installing silent prerequisites for features: A"
Any hints on why feature A preqs are installed?
--
HansO
We have a basic msi project with two features. The two features have opposite conditions so they can't be automatically selected.
Feature A - set level 200 when cA OR cB OR cC
Feature B - set level 200 when NOT(cA or cB or cC)
Both features have feature prerequisites.
We are experiencing when we try to install the setup file silently with /s /v" /qn" on machines that only qualify for feature B, the prereqs for Feature A get installed. When the same setup is installed using non-silent approach the correct prerequisites are installed. If we use /debuglog when running the setup file, we observe that InstallShield tries to install the prereqs before running the installer, and it says: "Installing silent prerequisites for features: A"
Any hints on why feature A preqs are installed?
--
HansO
(2) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Dec 04, 2012
10:45 AM
This probably depends on how the conditions cA, cB, and cC are determined. When running silently, the setup.exe bootstrap has to determine the feature states unless you specify them explicitly, and it can only handle certain minimal cases. The simplest workaround for your scenario should be to pass /v"ADDLOCAL=B" (or the real name of feature B) on your installation command line so that setup.exe knows exactly what will be installed.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Dec 05, 2012
02:03 AM
Hi Michael, and thanks for your quick reply.
That would explain it. The properties are set by System Search in the registry. Since the properties will not set Feature A to level 200, the Feature A will be installed.
That would explain it. The properties are set by System Search in the registry. Since the properties will not set Feature A to level 200, the Feature A will be installed.
![](/skins/images/CC38E504FC9E1309DC48ACFEB4925670/responsive_peak/images/icon_anonymous_message.png)