Software Deployment Question
Reevaluate Condition Question...
So, we have an install with some third party app integrations. What happens is that if an end user upgrades on of those apps after installing our software, which may support later versions, the end use launches our package again to run a Modify/Maintenance "Change" install. All works as planned. Our install detects the upgraded third party app and places the corresponding Features accordingly.
Now, here is the issue, there are also some conditioned components in our Core app that work in conjunction with the installed third party app. I thought I could just set those as transitive components by setting the Reevaluate Condition on them. However, as I understand it, these are only acted upon via Repair/"Reinstall". That won't work for us as the user won't want to run our package twice to match our components to their installed app. Also, I even tried running the repair and the conditioned components are still not installed when marked to reevaluate condition.
Is there any way I can get these transitive, conditioned components handled via the Maintenance/"Change" install?
I guess I could create new features to handle them and by adjusting ADDLOCAL at runtime to accomplish what I want, but that would be a lot of redesign/gutting. I'm hoping that I can deal with the components during Modify as they currently exist in our core app component tree.
Thank you so much in advance for any information or guidance you can provide! Oh, using InstallShield (BasicMSI project).
Be the first to answer this question