The names for the portions of a version are irrelevant to MSI. As long as the
first three portions of the version are higher (the common fourth part of the
version is ignored) that's a newer build... and your Upgrade table determines
the rest.
Here is the exact logic for the WiX toolset upgrade:
<!-- Major upgrade -->
<Upgrade Id="3618724B-2523-44F9-A908-866AA619504D">
<UpgradeVersion Minimum="$(var.WixVersion)" OnlyDetect="yes"
Property="NEWERVERSIONDETECTED" />
<UpgradeVersion Minimum="1.0.0.0" IncludeMinimum="yes"
Maximum="$(var.WixVersion)" IncludeMaximum="no"
Property="OLDERVERSIONBEINGUPGRADED" />
</Upgrade>
Note: We've never had a build number as low as "1.0.0.0" so that'll major
upgrade everything with a matching UpgradeCode.
-----Original Message-----
From: Robert O'Brien [mailto:[EMAIL PROTECTED]
Sent: Saturday, December 06, 2008 07:09
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] Announcement: WiX v3.0 beta exit release available
So the following sources associated with to enabling msi major upgrade support
will do major upgrade processing w/o concern for whether or not the "major"
number has changed in the product major.minor.build.revision number settings?
<Product Id="PUT-GUID-HERE"
Name="!(loc.ProductName)"
Language="1033" Version="3.0.4805.0"
Manufacturer="!(loc.ProductManufacturer)"
UpgradeCode=" PUT-UPGRADECODE-GUID-HERE ">
<Upgrade Id="PUT-UPGRADECODE-GUID-HERE">
<UpgradeVersion Minimum="3.0.4805.0" IncludeMinimum="yes" OnlyDetect="yes"
Property="NEWERVERSIONDETECTED" />
<UpgradeVersion Minimum="3.0.4513.0" IncludeMinimum="yes"
Maximum="3.0.4805.0" IncludeMaximum="no" Property="OLDERVERSIONDETECTED" />
</Upgrade>
<!-- for msi major upgrade processing -->
<CustomAction Id="SetMsiMajorUpgradePreventDowngradingError" Error="A newer
version of [ProductName] is already installed." />
<CustomAction Id="SetMsiMajorUpgradeReInstallProperty" Property="REINSTALL"
Value="ALL" />
<CustomAction Id="SetMsiMajorUpgradeReInstallModeProperty"
Property="REINSTALLMODE" Value="vomus" />
<InstallUISequence>
<!-- for msi major upgrade processing -->
<Custom Action="SetMsiMajorUpgradePreventDowngradingError"
After="FindRelatedProducts">NEWERVERSIONDETECTED</Custom>
<InstallExecuteSequence>
<!-- for msi major upgrade processing -->
<Custom Action="SetMsiMajorUpgradePreventDowngradingError"
After="FindRelatedProducts">NEWERVERSIONDETECTED</Custom>
<Custom Action="SetMsiMajorUpgradeReInstallProperty"
After="FindRelatedProducts">OLDERVERSIONDETECTED</Custom>
<Custom Action="SetMsiMajorUpgradeReInstallModeProperty"
After="FindRelatedProducts">OLDERVERSIONDETECTED</Custom>
<RemoveExistingProducts
After="InstallFinalize">OLDERVERSIONDETECTED</RemoveExistingProducts>
-----Original Message-----
From: Rob Mensching [mailto:[EMAIL PROTECTED]
Sent: Friday, December 05, 2008 3:39 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Announcement: WiX v3.0 beta exit release available
The WiX MSIs are all doing Major Upgrades. We're not being careful with the
MSI name nor the Componentization during day to day development to try to do
more optimal minor upgrade or patching. Major upgrades are just easier
(although less optimal).
-----Original Message-----
From: Robert O'Brien [mailto:[EMAIL PROTECTED]
Sent: Friday, December 05, 2008 08:34
To: 'WiX-users'
Subject: Re: [WiX-users] Announcement: WiX v3.0 beta exit release available
Great news and congratulations on reaching this milestone.
A while back I posted some questions to the forum about how to structure an msi
to automatically set REINSTALL and REINSTALLMODE property settings to necessary
values for patch and minor upgrade processing. There were working solutions
for the patch msp case but in the case of minor upgrade processing the remark
was made that you need to build a msi wrapper that launches it with
REINSTALL=ALL and REINSTALLMODE=vomus versus being able to automatically detect
minor upgrade scenarios and set those properties automatically within the msi.
Well it appears from my installation of the 3.0.4805.0 wix3_x64.msi that there
is some solution in place allowing you to just run the msi directly and for it
to determine a minor upgrade is necessary and set the required REINSTALL=ALL
and REINSTALLMODE= vomus property values so that the minor upgrade processing
can succeed. Any tips on how that was accomplished so it can be reused in
other wix authored msi work?
-----Original Message-----
From: Bob Arnson [mailto:[EMAIL PROTECTED]
Sent: Friday, December 05, 2008 6:28 AM
To: WiX-users
Subject: [WiX-users] Announcement: WiX v3.0 beta exit release available
The WiX Working Group is pleased to announced that the WiX v3.0 "beta
exit" build (v3.0.4805.0) is now available. We encourage all users to
upgrade to this build for the latest fixes and to verify how ready WiX
v3.0 is for release. For more information, see Rob's announcement
<http://robmensching.com/blog/archive/2008/11/29/WiX-v3-toolset-end-of-the-Beta-imminent.aspx>,
my follow-up
<http://www.joyofsetup.com/2008/11/29/wix-v30-beta-coming-soon/>, and
Highlights of WiX v3.0.4805.0
<http://www.joyofsetup.com/2008/12/05/highlights-of-wix-v3048050/>.
You can download it from http://wix.sourceforge.net/releases/3.0.4805.0/
or from the WiX SourceForge.net releases page
<https://sourceforge.net/project/showfiles.php?group_id=105970&package_id=168888&release_id=645083>.
*
*
--
sig://boB
http://joyofsetup.com/
------------------------------------------------------------------------------
SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada.
The future of the web can't happen without you. Join us at MIX09 to help
pave the way to the Next Web now. Learn more and register at
http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/
_______________________________________________
WiX-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wix-users
------------------------------------------------------------------------------
SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada.
The future of the web can't happen without you. Join us at MIX09 to help
pave the way to the Next Web now. Learn more and register at
http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/
_______________________________________________
WiX-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wix-users
------------------------------------------------------------------------------
SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada.
The future of the web can't happen without you. Join us at MIX09 to help
pave the way to the Next Web now. Learn more and register at
http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/
_______________________________________________
WiX-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wix-users
------------------------------------------------------------------------------
SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada.
The future of the web can't happen without you. Join us at MIX09 to help
pave the way to the Next Web now. Learn more and register at
http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/
_______________________________________________
WiX-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wix-users
------------------------------------------------------------------------------
SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada.
The future of the web can't happen without you. Join us at MIX09 to help
pave the way to the Next Web now. Learn more and register at
http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/
_______________________________________________
WiX-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wix-users
