Hello,
Thus I was confused what is the best practice for using such UI values to condition other elements?
There are the
package INSTALLLEVEL values which you listed and there are
individual features'
Level values. You can set each feature's level from the Organization page -> Your_Feature -> "Install based on condition" -> "Set additional install conditions" ->
Edit Conditional Level Dialog.
Basically the package INSTALLLEVEL will be set depending on what the user choses in the SetupTypeDlg or by the default value (silent installation). Subsequently, all features that have a level value which is less or equal than the package INSTALLLEVEL, will be installed.
For more information about INSTALLLEVEL property you can
follow MSDN.
Then that would be used to condition features, instead of just the overall InstallMode property?
Conditioning features can be done from "Install based on condition" field I mentioned above. A feature's condition depends on the installer architecture which is dictated by the software you're installing. What exactly do you mean by this?
Again, if you're looking to condition custom actions depending on features you could use something like:
This condition will be true only if the feature "Feature" will be installed locally. If the feature is not selected for installation the condition is false. You can read more from
Edit Condition Dialog.
All the best,
Mihai
FOLLOW US
Get the latest news in Application Packaging