That sounds pretty bizarre. Which bootstrapper are you using which is causing that? A bootstrapper should either simply ShellExecute your MSI or call msiexec.exe /i (which amount to the same thing essentially). I don't think you can set something like "Installed" on the command line, AFAIK only public properties can be passed to msiexec.exe so I've no idea how that's even possible. Does your original code work properly when you run the MSI without the bootstrapper? Are you sure the bootstrapper isn't setting REINSTALL when it launches your MSI?
Your conditions look fine if you're never going to use MSPs. You need to set REINSTALL when applying an MSP so it'd thoroughly break those conditions but as long as you're happy to live without them they should be OK. I don't think they'll interfere with major upgrades but I would test it first. Palbinder Sandher Software Deployment & IT Administrator T: +44 (0) 141 945 8500 F: +44 (0) 141 945 8501 http://www.iesve.com **Design, Simulate + Innovate with the <Virtual Environment>** Integrated Environmental Solutions Limited. Registered in Scotland No. SC151456 Registered Office - Helix Building, West Of Scotland Science Park, Glasgow G20 0SP Email Disclaimer -----Original Message----- From: Rob Hamflett [mailto:r...@snsys.com] Sent: 06 April 2010 10:43 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Problem using 'Installed' as a condition 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 ------------------------------------------------------------------------------ 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
