The RemoveExistingProducts documentation details four locations where it can be sequenced. The third location is between the InstallExecute/InstallExecuteAgain action and the Installfinalize action. Neither InstallExecute nor InstallExecuteAgain is automatically included in the sequence -- it's up to the installation designer to manually include them.
The documentation on InstallExecute and InstallExecuteAgain says what the actions do, but not why they would be put in, or in what ways their inclusion changes the overall installation process. Can someone provide some context about what goes on behind the scenes that would make these actions desireable or necessary, and why REP has a relationship to them? I didn't find anything in MSDN or Phil's book that went into any detail. It's also not clear whether things can/should be sequenced between REP and InstallFinalize. (Request Context) I'm trying to push the REP position in an existing installer from before InstallInitialize into the script somewhere so I can add CA's to back up configuration files, and I'm trying to figure out where the best place is. Thanks! James Scott ------------------------------------------------------------------------------ Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users