I have discovered an issue with using 'Installed' as a condition for InstallExecuteSequence entries. I have some actions that generally go as follows:
<...> <MyRemoveAction>REINSTALL OR Installed</MyRemoveAction> <RemoveFiles /> <...> <InstallFiles /> <MyInstallAction>REINSTALL OR NOT Installed</MyInstallAction> <...> The problem is that my installer is being run by a bootstrapper that isn't checking if the product is already installed, so it is going through some kind of maintenance mode where Installed is set but REINSTALL isn't. This results in MyRemoveAction being performed, but not MyInstallAction, which leaves me with a broken installation. I can reproduce this by reinstalling it myself and passing the /qb flag to msiexec. I'm going to talk to the people who make the bootstrapper, but I was wondering if the following conditions would be usable, and if anyone could see anything obvious that will bite me. All upgrades we do are major, no patches. For MyRemoveAction: REINSTALL OR REMOVE="ALL" For MyInstallAction: REINSTALL OR NOT REMOVE Thanks, Rob ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
