Sounds like you should probably schedule CopyFiles before RemoveFiles and/or InstallFiles (not sure of their default sequencing relative to one another), and re-schedule RemoveExistingProducts to just before or after InstallFinalize (instead of InstallInitialize). This is all done in the InstallExecute sequence.
Cody On 10/7/08 4:03 PM, "Joshua Chambers" <[EMAIL PROTECTED]> wrote: Hello! So I am working on a new version of a program already out in the field. Thanks to a finger pointing in the right direction I have gotten the new installer to run when clicked on (before, the old one ran), now I have my upgrade stuff working fine and dandy, though I have just one problem. There is one file from the old version that I want to back up before it's removed. I see this CopyFile action, but I don't see where I can use it productively since the removing of the old version seems to happen pretty much behind the scenes, and the Component tag for the replacement file is not active until the installer part is running, after FindRelatedProducts has already run and removed the file. At what point can I stick an action in here to back this file up before the uninstall carries on? Thank you! Joshua ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
