Bob Arnson wrote: > Backup can be done as an immediate custom action, so you don't need a > deferred CA: Just read the configuration data into custom action data > and schedule a deferred CA just before InstallFinalize to write it back.
I appreciate that response. However, I don't want solving my immediate problem to get in the way of actually learning about what is going on. The original questions I had were: > 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. Do you (collectively) have any pointers on where I can acquire the contextual information I'm looking for? 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
