1 reply to this topic

[KathyMorey]

Basic MSI, IS DevStudio 9 SP1

I have an addin that is authored to run without any dialogs, by using AppSearch to read settings from the main product, which must be installed first. It also has a VBScript custom action to take a registry string and parse it to determine which features are licensed and can be installed, by setting properties that are conditions on the features of the addin.

Install, repair, remove and upgrades are all working well.

However, when the main product is modified, and the license string is changed, a custom action kicks off the add-in with REINSTALL=ALL and REINSTALLMODE=omus. That combination reinstalls what was originally installed despite any changes made to the license string - in other words, the feature states aren't being re-evaluated according to the properties being set.

How do I get the addin project to re-evaluate the feature states so that it will install new features and uninstall deleted features? What gets set when you run an msi from the Add/Remove applet and select "modify"?

[Stefan Krueger]

Try without REINSTALL on the command line. Instead set the features states inside your setup, based on the results of the VBScript (or even try setting ADDLOCAL and REMOVE properties from inside your script). I don't think Feature conditions are appropriate for that purpose. Note also the following quote from MSI Help: