MAJOR UPGRADE = PRODUCT CODE (produ...@id) IS DIFFERENT (VERSION DOESN'T MATTER, EXCEPT IN UPGRADE TABLE)
MINOR UPGRADE/MINOR UPDATE = PRODUCT CODE IS SAME, VERSION IS DIFFERENT (UPGRADE TABLE IS IGNORED) SMALL UPDATE = PRODUCT CODE AND VERSION ARE SAME (UPGRADE TABLE IS IGNORED) -----Original Message----- From: Galuza Michael [mailto:mdgal...@dejarnette.com] Sent: Thursday, December 30, 2010 9:03 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Is upgrading without caching possible. Finally got it working. I realized I missed one very important part of Major Upgrades... you have to change the Product code. On top of that I had to run the install without REINSTALL=ALL and without the "v" in the REINSTALLMODE (i.e. REINSTALLMODE=omus). It finally seems to be working. Sorry to have cluttered this discussion list as I worked my way through this when the main problem was I didn't read the fine print carefully enough to realize that I needed to change the Product code. Thanks for the help. -----Original Message----- From: Galuza Michael [mailto:mdgal...@dejarnette.com] Sent: Thursday, December 30, 2010 10:42 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Is upgrading without caching possible. Okay, but what about files that don't include a version, such as a text file? I did more research and found a suggestion to schedule my RemoveExistingProducts earler (I had it after InstallFinalize) so I moved it to after InstallInitialize. I was hoping it would remove the old file so tht it wouldn't be overwriting it. I got the same results, but decided to look at my log to see what was happening in RemoveExistingProducts. The log said "Skipping RemoveExistingProdicts action: current configuration is maintenance mode or an uninstall". Any idea what that is about? Why is it skipping RemoveExistingProducts? -----Original Message----- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Thursday, December 30, 2010 10:14 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Is upgrading without caching possible. For the new installer, you must increase the "file version" in the file's version resource. The installer considers two files with the same path, filename and version number to be the same file. http://msdn.microsoft.com/en-us/library/aa368267%28VS.85%29.aspx -----Original Message----- From: Galuza Michael [mailto:mdgal...@dejarnette.com] Sent: 30 December 2010 16:01 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Is upgrading without caching possible. In looking at the install log, I see the below error when it goes to copy the file. How does it determine the version of the file? The file is, in fact a newer file, but I didn't update the version in the binary of the file. Is that what it is using to determine the version? Is there a way to override that so it will blindly overwrite it? MSI (s) (30:D0) [09:32:09:283]: File: C:\Program Files\XXX\UpgradeTest\bin\xxx.exe; Won't Overwrite; Won't patch; Existing file is of an equal version -----Original Message----- From: Galuza Michael [mailto:mdgal...@dejarnette.com] Sent: Thursday, December 30, 2010 9:36 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Is upgrading without caching possible. However, you seem to be somewhat correct. I renamed the new msi file to match the name of the old one and the worked! Well, it completed with no visible errors anyway. When I look in "Add/Remove Programs" the version has been updated. However, the one file in the install did NOT get upgraded. Any suggestions on that? -----Original Message----- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Thursday, December 30, 2010 9:18 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Is upgrading without caching possible. You can't change the MSI file name in a minor upgrade. You can only do it in a major upgrade. -----Original Message----- From: Galuza Michael [mailto:mdgal...@dejarnette.com] Sent: 30 December 2010 15:05 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Is upgrading without caching possible. I decided to put together a very simple example to test all this out. I took my 2 installs, removed everything except one file, removed the GUI, etc. As expected and hoped, I still get the same problem. I'm including my .wxs files below. Can someone please help me figure out what I'm doing wrong? I install the first version, no problem. As expected, If I just double click the newer version I get the "Another version of this product is already installed..." error. So I try various versions of running msiexec and here are the results: Msiexec /I xxx51.msi REINSTALL=ALL REINSTALLMODE=vomus This results in the error "A network error occurred while attempting to read from the file C:\xxx4.msi" (the old MSI file). So I tried this removing the "v" to avoid trying to use the cached MSI: Msiexec /I xxx51.msi REINSTALL=ALL REINSTALLMODE=omus This again results in the "Another version of this product is already installed ..." error. Somewhere during my research I found a suggestion that REINSTALL should not be specified. So I tried this: Msiexec /I xxx51.msi REINSTALLMODE=omus Again I got the "Another version of this product is already installed ..." error. So, for the heck of it I tried this: Msiexec /I xxx51.msi REINSTALLMODE=vomus And I again got the "Network error". I'm assuming there is something I'm doing wrong in my .wxs file. Is there a good tutorial on upgrades somewhere (other than this one: http://www.tramontana.co.hu/wix, since it clearly steered me wrong)? Or can someone please help me figure out what I'm doing wrong in this simple example? Thanks Here are my wxs files for the above example, old version, followed by new version: <?xml version="1.0" encoding="utf-8"?> <Wix xmlns="http://schemas.microsoft.com/wix/2006/wi"; xmlns:iis="http://schemas.microsoft.com/wix/IIsExtension"; xmlns:util="http://schemas.microsoft.com/wix/UtilExtension";> <Product Name="Upgrade Test" Version="4.00.0008" Manufacturer="xxx, Inc." Id="CB198571-04A9-420e-BDA7-C8D3B4CDEF76" Language="1033" UpgradeCode="FC6A5B6C-04EA-43a2-8634-22CFBF0BD3A9"> <Package Id="*" Keywords="Installer" Description="Upgrade Test" Manufacturer="xxx, Inc." InstallerVersion="300" Languages="1033" SummaryCodepage="1252" /> <Media Id="1" Cabinet="Data1.cab" EmbedCab="yes" DiskPrompt="CD-ROM #1" /> <Property Id="DiskPrompt" Value="Upgrade Test[1]" /> <Directory Id="TARGETDIR" Name="SourceDir"> <Directory Id="ProgramFilesFolder" Name="Program Files"> <Directory Id="XXX" Name="XXX"> <Directory Id="INSTALLDIR" Name="UpgradeTest"> <Directory Id="XXBIN" Name="bin"> <Component Id="xxxService" Guid="2A8EF740-64D3-4853-A549-EFC07C0A0F49" SharedDllRefCount="yes"> <File Id="xxx.exe" Name="xxx.exe" Compressed="yes" KeyPath="yes" DiskId="1" Source=".\xxx4.exe" /> </Component> </Directory> </Directory> </Directory> </Directory> </Directory> <Feature Id="UDT" Title="Update Test" Level="1" ConfigurableDirectory="INSTALLDIR" Absent="disallow" AllowAdvertise="no"> <ComponentRef Id="xxxService" /> </Feature> <!-- Not sure if this is needed, but ARPINSTALLLOCATION seems to be something related to Windows Installer, so it can't do any harm to leave it in I suppose. --> <CustomAction Id="SetARPINSTALLLOCATION" Return="check" Property="ARPINSTALLLOCATION" Value="[INSTALLDIR]" /> <InstallExecuteSequence> <!-- Not sure if this is needed, but ARPINSTALLLOCATION seems to be something related to Windows Installer, so it can't do any harm to leave it in I suppose. --> <Custom Action="SetARPINSTALLLOCATION" After="CostFinalize"><![CDATA[Not Installed]]></Custom> </InstallExecuteSequence> </Product> </Wix> <?xml version="1.0" encoding="utf-8"?> <Wix xmlns="http://schemas.microsoft.com/wix/2006/wi"; xmlns:iis="http://schemas.microsoft.com/wix/IIsExtension"; xmlns:util="http://schemas.microsoft.com/wix/UtilExtension";> <Product Name="Upgrade Test" Version="5.01.0001" Manufacturer="xxx, Inc." Id="CB198571-04A9-420e-BDA7-C8D3B4CDEF76" Language="1033" UpgradeCode="FC6A5B6C-04EA-43a2-8634-22CFBF0BD3A9"> <Package Id="*" Keywords="Installer" Description="Upgrade Test" Manufacturer="xxx, Inc." InstallerVersion="300" Languages="1033" SummaryCodepage="1252" /> <Upgrade Id='FC6A5B6C-04EA-43a2-8634-22CFBF0BD3A9'> <UpgradeVersion OnlyDetect="no" Property="VPRE4FOUND" Maximum='4.00.0008' IncludeMaximum='no' /> <UpgradeVersion OnlyDetect='no' Property="V4FOUND" Minimum='4.00.0008' IncludeMinimum='yes' Maximum='4.00.0008' IncludeMaximum='yes' /> <UpgradeVersion OnlyDetect='no' Property="V50FOUND" Minimum='4.00.0008' IncludeMinimum='no' Maximum='5.01.0001' IncludeMaximum='no'/> <UpgradeVersion OnlyDetect='yes' Property="V51FOUND" Minimum='5.01.0001' IncludeMinimum='yes' Maximum='5.01.0001' IncludeMaximum='yes' /> <UpgradeVersion OnlyDetect='no' Property="POSTV51FOUND" Minimum='5.01.0001' IncludeMinimum='no'/> </Upgrade> <CustomAction Id="CurrVerTooOld" Error='You can only upgrade to [ProductName] V5.1 from V4.0 build 8 or higher.' /> <CustomAction Id="NoDowngrade" Error='A later version of [ProductName] is already installed.' /> <CustomAction Id="AlreadyInstalled" Error='[ProductName] V5.1 is already installed.' /> <Media Id="1" Cabinet="Data1.cab" EmbedCab="yes" DiskPrompt="CD-ROM #1" /> <Property Id="DiskPrompt" Value="Upgrade Test[1]" /> <Directory Id="TARGETDIR" Name="SourceDir"> <Directory Id="ProgramFilesFolder" Name="Program Files"> <Directory Id="XXX" Name="XXX"> <Directory Id="INSTALLDIR" Name="UpgradeTest"> <Directory Id="XXXBIN" Name="bin"> <Component Id="xxxService" Guid="2A8EF740-64D3-4853-A549-EFC07C0A0F49" SharedDllRefCount="yes"> <File Id="xxx.exe" Name="xxx.exe" Compressed="yes" KeyPath="yes" DiskId="1" Source=".\xxx51.exe" /> </Component> </Directory> </Directory> </Directory> </Directory> </Directory> <Feature Id="UDT" Title="Update Test" Level="1" ConfigurableDirectory="INSTALLDIR" Absent="disallow" AllowAdvertise="no"> <ComponentRef Id="xxxService" /> </Feature> <!-- Not sure if this is needed, but ARPINSTALLLOCATION seems to be something related to Windows Installer, so it can't do any harm to leave it in I suppose. --> <CustomAction Id="SetARPINSTALLLOCATION" Return="check" Property="ARPINSTALLLOCATION" Value="[INSTALLDIR]" /> <InstallExecuteSequence> <!-- Not sure if this is needed, but ARPINSTALLLOCATION seems to be something related to Windows Installer, so it can't do any harm to leave it in I suppose. --> <RemoveExistingProducts After='InstallFinalize' /> <Custom Action="SetARPINSTALLLOCATION" After="CostFinalize"><![CDATA[Not Installed]]></Custom> <Custom Action="CurrVerTooOld" After='FindRelatedProducts'>VPRE4FOUND</Custom> <Custom Action='NoDowngrade' After='FindRelatedProducts'>POSTV51FOUND</Custom> <Custom Action='AlreadyInstalled' After='FindRelatedProducts'>V51FOUND</Custom> </InstallExecuteSequence> </Product> </Wix> -----Original Message----- From: Rob Mensching [mailto:r...@robmensching.com] Sent: Wednesday, December 29, 2010 4:26 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Is upgrading without caching possible. The Upgrade element is only used for major upgrades. Minor upgrades are a different (often more difficult) mechanism for upgrading. The MSI SDK has a few great pages about the differences between Major and Minor upgrades. I typically recommend major upgrades. On Wed, Dec 29, 2010 at 9:58 AM, Galuza Michael <mdgal...@dejarnette.com>wrote: > I've been trying to do an upgrade and everything I try gives me one of 3 > results: > > > > 1) I immediately get a message saying another version of the product > is installed, installation can't continue. > > 2) The install goes into maintenance mode and asks me if I want to > Repair or uninstall. > > 3) The system tries to access the cached version of the previous MSI > (which is not available) and I get a message saying there was a network > error trying to access the old MSI. > > > > I started out by using the instructions for an upgrade here: > http://www.tramontana.co.hu/wix/. I tried implementing a minor upgrade > by setting Upgrade/UpgradeVersion/@OnlyDetect to "yes" and running this: > > > > Msiexec /I x.msi REINSTALL=ALL REINSTALLMODE=vomus > > > > This resulted in error #3. After looking through this discussion list > I've tried various suggestions and ideas, such as doing a major upgrade > by setting OnlyDetect to "no", removing the "v" from REINSTALLMODE > and/or removing the REINSTALL option entirely. Every combination gives > me one of the 3 errors above. > > > > Here is the important wxs "code" from my "old" install (the entire file > is VERY big so I'm not posting all of it): > > > > <?xml version='1.0' encoding='windows-1252'?> > > <Wix xmlns='http://schemas.microsoft.com/wix/2003/01/wi'> > > <Product Name="xxx" Version="4.00.0008" Manufacturer="xxx, Inc." > Id="E881549F-8E1E-4272-A833-9B5A36697BB5" Language="1033" > UpgradeCode="6FF33788-50F7-4e37-B240-BC3AF1B7A71B" > > > > > <Package Id='????????-????-????-????-????????????' > Keywords='Installer' > > Description="xxx" > > Manufacturer='xxx, Inc.' > > InstallerVersion='200' Languages='1033' SummaryCodepage='1252' /> > > > > Here is the wxs code from my new install (or the latest incarnation of > it anyway): > > > > <?xml version="1.0" encoding="utf-8"?> > > <Wix xmlns="http://schemas.microsoft.com/wix/2006/wi"; > xmlns:iis="http://schemas.microsoft.com/wix/IIsExtension"; > xmlns:util="http://schemas.microsoft.com/wix/UtilExtension";> > > <Product Name="PACSWare Intelligent Router" Version="5.01.0001" > Manufacturer="DeJarnette Research Systems, Inc." > Id="E881549F-8E1E-4272-A833-9B5A36697BB5" Language="1033" > UpgradeCode="6FF33788-50F7-4e37-B240-BC3AF1B7A71B"> > > <Package Id="*" Keywords="Installer" Description="PACSWare > Intelligent Router" Manufacturer="DeJarnette Research Systems, Inc." > InstallerVersion="300" Languages="1033" SummaryCodepage="1252" /> > > > > <Upgrade Id='6FF33788-50F7-4e37-B240-BC3AF1B7A71B'> > > <UpgradeVersion OnlyDetect="no" Property="VPRE4FOUND" > > Maximum='4.00.0008' IncludeMaximum='no' /> > > <UpgradeVersion OnlyDetect='no' Property="V4FOUND" > > Minimum='4.00.0008' IncludeMinimum='yes' > > Maximum='4.00.0008' IncludeMaximum='yes' /> > > <UpgradeVersion OnlyDetect='no' Property="V50FOUND" > > Minimum='4.00.0008' IncludeMinimum='no' > > Maximum='5.01.0001' IncludeMaximum='no'/> > > <UpgradeVersion OnlyDetect='no' Property="V51FOUND" > > Minimum='5.01.0001' IncludeMinimum='yes' > > Maximum='5.01.0001' IncludeMaximum='yes' /> > > <UpgradeVersion OnlyDetect='no' Property="POSTV51FOUND" > > Minimum='5.01.0001' IncludeMinimum='no'/> > > </Upgrade> > > > > <CustomAction Id="CurrVerTooOld" Error='You can only upgrade to > [ProductName] V5.1 from V4.0 build 8 or higher.' /> > > <CustomAction Id="NoDowngrade" Error='A later version of > [ProductName] is already installed.' /> > > <CustomAction Id="AlreadyInstalled" Error='[ProductName] V5.1 is > already installed.' /> > > > > I've always been able to figure out any WIX problems I've had by > searching the internet, but this one has me stumped. So any help or > suggestions are appreciated. > > > > Thanks, > > Mike > ------------------------------------------------------------------------ ------ Learn how Oracle Real Application Clusters (RAC) One Node allows customers to consolidate database storage, standardize their database environment, and, should the need arise, upgrade to a full multi-node Oracle RAC database without downtime or disruption http://p.sf.net/sfu/oracle-sfdevnl _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users SDL PLC confidential, all rights reserved. If you are not the intended recipient of this mail SDL requests and requires that you delete it without acting upon or copying any of its contents, and we further request that you advise us. SDL PLC is a public limited company registered in England and Wales. Registered number: 02675207. Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6 7DY, UK. ------------------------------------------------------------------------ ------ Learn how Oracle Real Application Clusters (RAC) One Node allows customers to consolidate database storage, standardize their database environment, and, should the need arise, upgrade to a full multi-node Oracle RAC database without downtime or disruption http://p.sf.net/sfu/oracle-sfdevnl _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------ ------ Learn how Oracle Real Application Clusters (RAC) One Node allows customers to consolidate database storage, standardize their database environment, and, should the need arise, upgrade to a full multi-node Oracle RAC database without downtime or disruption http://p.sf.net/sfu/oracle-sfdevnl _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------ ------ Learn how Oracle Real Application Clusters (RAC) One Node allows customers to consolidate database storage, standardize their database environment, and, should the need arise, upgrade to a full multi-node Oracle RAC database without downtime or disruption http://p.sf.net/sfu/oracle-sfdevnl _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------ ------ Learn how Oracle Real Application Clusters (RAC) One Node allows customers to consolidate database storage, standardize their database environment, and, should the need arise, upgrade to a full multi-node Oracle RAC database without downtime or disruption http://p.sf.net/sfu/oracle-sfdevnl _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------ ------ Learn how Oracle Real Application Clusters (RAC) One Node allows customers to consolidate database storage, standardize their database environment, and, should the need arise, upgrade to a full multi-node Oracle RAC database without downtime or disruption http://p.sf.net/sfu/oracle-sfdevnl _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ---------------------------------------------------------------------------- -- Learn how Oracle Real Application Clusters (RAC) One Node allows customers to consolidate database storage, standardize their database environment, and, should the need arise, upgrade to a full multi-node Oracle RAC database without downtime or disruption http://p.sf.net/sfu/oracle-sfdevnl _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ Learn how Oracle Real Application Clusters (RAC) One Node allows customers to consolidate database storage, standardize their database environment, and, should the need arise, upgrade to a full multi-node Oracle RAC database without downtime or disruption http://p.sf.net/sfu/oracle-sfdevnl _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
