We built an MSI package which installs several other Chained packages. To improve the user experience, we associated a Feature with each Chained package allowing the user to choose which Chained package to install. (Customize/Modify). The exercise has an adverse effect which we need your help to overcome.
Our configuration allows the user to go to Programs/Features and modify the configuration of the package. If a previously installed feature is removed, the uninstall process also uninstalls the associated Chained package.
If the user chooses to install a feature (it’s associated chained packaged is not installed), the components associated with the feature (registry entries, files) are installed but the associated chained package fails to installs. Close examination of the log files indicates that MSI is attempting to reinstall the chained package instead of installing it.
Is there a method/PROPERTY we can use to force a chained package to install at a later time when the user decides to modify the package configuration?
Thanks
JL
FOLLOW US
Get the latest news in Application Packaging