Hey, Thanks. So does this mean that in the case of drastic upgrading - component removal etc - would it be a better idea to completely remove the product under upgrade and then install?
./Ali On Dec 12, 2007, at 12:45 PM, Bob Arnson wrote: > Ali-Akber Saifee wrote: >> * everything is kept the same except the version and the package >> code. >> * the second package contains new binaries, but actually has a few >> components removed, and some custom actions removed. >> >> upon running the second installer in upgrade mode (msiexec /fvomus >> Product.msi /qf) - the upgrade is semi-successful. the binaries >> that have newer versions in the new package get updated, but the >> ones that need to be removed - remain. Upon uninstallation of this >> upgraded installation, the files that weren't present in the >> second installer don't get removed! >> > > You're telling MSI that the new package replaces the old one; > there's nothing that tells MSI that the files were removed or that > it needs to keep track of them any longer. See "Changing the Product > Code" in the MSI SDK for details about removing components: Short > version is that you should avoid it if possible. > > -- > sig://boB > http://joyofsetup.com/ > > ------------------------------------------------------------------------- SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
