Two threads have brought this up, so I'll repost this:
Figure out why the upgrade is removing the file because it's not inevitable. 1. You should add the file in question to your new setup with the same component guid. If you haven't got it in the new install then clearly it will be removed during an upgrade because that file is no longer in the later version of the product. 2. Then, if RemoveExistingProducts is late in the upgrade AND the existing data file has been modified after it was installed by the older product then it will not be removed because of the file replacement rules. File replacement rules: * http://msdn.microsoft.com/en-us/library/windows/desktop/aa370532(v=vs.85).as *px People are always upgrading their products without uninstalling databases and other data files, and this is the way it's done. Modified files don't get overwritten (see 1) and RemoveExistingProducts at the end of the install (see 2) is the way to do that. Phil W ------------------------------------------------------------------------------ Get 100% visibility into Java/.NET code with AppDynamics Lite! It's a free troubleshooting tool designed for production. Get down to code-level detail for bottlenecks, with <2% overhead. Download for free and get started troubleshooting in minutes. http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
