Yeah I found that the file versioning rules was exactly my problem, because I was trying to overwrite an exe with version with an empty exe(ie. has no versions), no wonder it didn't work. Thanks for your help! Sent from my BlackBerry® wireless device
-----Original Message----- From: "Mike Dimmick" <[EMAIL PROTECTED]> Date: Wed, 16 Jan 2008 22:06:58 To:"'Roger Yen'" <[EMAIL PROTECTED]>,<wix-users@lists.sourceforge.net> Subject: RE: [WiX-users] major upgrade with merger module It’s a bit hard to know where to start. Was this a major upgrade, that is, did you change the Product Id? Did you author the Upgrade table to remove the existing version? Where did you schedule the RemoveExistingProducts action? Did you change the Component IDs at all? You should really leave them the same if the files are compatible; conversely, if they’re not compatible, you’re supposed to change the component GUID and ensure that the files are installed to a different (full) path (i.e. change the name or put it elsewhere). Windows Installer uses the KeyPath for a component to determine if the component is already installed and therefore whether to skip installing it. Finally, if Windows Installer detects that a component to be installed is already present, it uses file versioning rules to decide whether to keep the existing version of the component or whether to install the version in the package. The rules basically are: - If both files have a version number in their resources, the highest version number wins; - If one file has a version number and the other doesn’t, the file with the version number wins; - If neither file has a version, if the installed file has a modified date later than its creation date (reflecting a change made by the user), or if the file hash matches the hash in the MsiFileHash table, it is kept, otherwise it is overwritten. The practical consequence of this is that you must always increment version numbers and you should always version DLLs, EXEs and anything else that supports versioning through resources. -- Mike Dimmick ---------------- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Roger Yen Sent: 16 January 2008 21:02 To: wix-users@lists.sourceforge.net Subject: [WiX-users] major upgrade with merger module Hi, I'm using WIX v3, and I've built an installer that installs an exe file, using modules, now I'm trying to test the major upgrade feature, by replacing the exe file with another one and adding a txt to the installed folder. I tried first installing a 1 KB dummy exe and replacing it with the real exe file, and it worked fine. However when I tried doing it the opposite way, ie. installing the real exe and attempting to "upgrade" it to the dummy file, the installation just simply wouldn't install anything, not even the shortcuts. But when I target the install path to something different, the installation worked fine again. This is rather weird and I have no idea why this is happening, since the only difference between the two approaches is changing the source files in the <File....../>. Does anyone know what could be the problem here? I can post my code if needed. Thank you. ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
