[wix-users] WiX MSI Failing to upgrade all components
Colin.Sim at ipfx.com
Sun Dec 13 10:37:32 PST 2015
I can confirm that the file version and product version attributes of the BackupUtil.exe component is being updated between components. We stamp all our components (.exe, .dll, dot anything that can have a file or product version) and installer on every build. So I do not believe this is the cause of the error I'm seeing.
From: wix-users [mailto:wix-users-bounces at lists.wixtoolset.org] On Behalf Of Robert Beardsworth
Sent: Monday, 14 December 2015 7:11 a.m.
To: WiX Toolset Users Mailing List <wix-users at lists.wixtoolset.org>
Subject: Re: [wix-users] WiX MSI Failing to upgrade all components
quick simple question: did you mess with the File Versions of your BackupUtil.exe? I am sure someone will correct me if I am wrong, but I believe that the Windows installer uses the File Version to decide whether to overwrite files (we bumped into this when producing interop files with tlbimp which didn't produce a new File Version unless we changes the assembly version).
> From: Colin.Sim at ipfx.com
> To: wix-users at lists.wixtoolset.org
> Date: Sun, 13 Dec 2015 09:21:20 +0000
> Subject: [wix-users] WiX MSI Failing to upgrade all components
> This question relates to this past post http://lists.wixtoolset.org/pipermail/wix-users-wixtoolset.org/2015-July/000014.html but now I have had time to reproduce the error on a much smaller scale with logs I can hopefully upload to the mailing list.
> I have an installer that contains a single component (this is the simplified case). I have created two installers:
> - ServerInstaller.1.0.0.msi, which contains BackupUtil.exe version 6.4.70.
> - ServerInstaller.1.0.1.msi, which contains BackupUtil.exe version 6.4.71.
> After ServerInstaller.1.0.0.msi is installed and BackupUtil.exe is manually replaced with a higher version, say 6.4.78, when I run ServerInstaller.1.0.1.msi, BackupUtil.exe gets removed. I am expecting it to be left alone.
> I couldn't see anything obvious that is wrong apart from perhaps "Skipping RemoveExistingProducts action: current configuration is maintenance mode or an uninstall". I am very new installer is correctly updated to perform a major upgrade, i.e. there is a new ProductCode, new PackageCode, and version number. The UpgradeCode remains the same.
> I have attached the logs to this post; hopefully, someone can see the thing I'm doing wrong.
> PS: I am observing this same type of behaviour on our old installers that are authored in InstallShield. So my gut is telling me this is something fundamentally wrong with Windows Installer itself.
> This e-mail contains IPFX information which may be privileged or confidential and is intended for use only by the individual(s) or entity named above. If you are not the intended recipient, note that disclosing, copying, distributing or using this information is prohibited. If you have received this e-mail in error, please advise immediately to the e-mail address above and permanently delete this message and any attachments. Please note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of the company. We monitor our e-mail system and may record your e-mails. Thank you.
> WiX Toolset Users Mailing List provided by FireGiant http://www.firegiant.com/
WiX Toolset Users Mailing List provided by FireGiant http://www.firegiant.com/
More information about the wix-users