UpgradeCode. Take a spin through the MSI SDK about all the different ways
Upgrades can be accomplished. It's terse but you'll learn a lot.
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Alex Henderson
Sent: Tuesday, February 27, 2007 1:44 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Help getting upgrades to work
Thanks Mike,
Ok, just tried that and the installer runs when a previous version is
installed, which is great... however both version appear in the add/remove
programs menu now, so it appears changing the product Id has caused MSI to
think it's an entirely different product?
Any ideas what I'm doing wrong... and out of curiosity, how does MSI know a
previous version of the same product is installed if the products identifier is
no longer the same...(does it use the upgrade code of the previous installed
version / this version to match up?
Chez,
- Alex
From: Mike Poulson [mailto:[EMAIL PROTECTED]
Sent: Wednesday, 28 February 2007 10:28 a.m.
To: 'Alex Henderson'; wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] Help getting upgrades to work
Change your product id. What you are doing is a Major upgrade in the eyes of
MSI.
Mike Poulson
Network Engineer
Tableau Software
400 North 34th Street, Suite 200
Seattle, WA 98103
206 633 3400 x.556
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Alex Henderson
Sent: Tuesday, February 27, 2007 1:12 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Help getting upgrades to work
I'm still getting to grips with WiX... my current problem is trying to figure
out how I can get upgrades to work.
What I'm looking to do is just have later versions of the same product
uninstall the previously version and install the new version (At this point I'd
be quite happy if it was silent...).. here's what I've got so far, the
PRODUCTBUILDVERSION variable is a 2 part version number (such as 9.122) with
the last part being aligned with our build numbers.
So I did this:
<Upgrade Id="58acbe6b-ffd2-4c7d-97a3-6b16f7d76384">
<UpgradeVersion Minimum="0.0.0.0"
IncludeMinimum="yes"
Maximum="0.0.$(var.PRODUCTBUILDVERSION)"
IncludeMaximum="no"
Property="PREVIOUSVERSIONFOUND"/>
<UpgradeVersion OnlyDetect="yes"
Property="NEWERVERSIONFOUND"
Minimum="0.0.$(var.PRODUCTBUILDVERSION)"
IncludeMinimum="no"/>
</Upgrade>
And then...
<CustomAction Id="NoDowngrade" Error="A later version of [ProductName] is
already installed!" />
<InstallExecuteSequence>
<Custom Action="NoDowngrade"
After="FindRelatedProducts">NEWERVERSIONFOUND</Custom>
<RemoveExistingProducts Before="InstallInitialize"/>
</InstallExecuteSequence>
But when the version number changes up, say from 0.0.9.121, to 0.0.9.122, the
product displays the usual error dialog:
"Another version of this product is already installed. Installation of this
version cannot continue. To configure or remove the existing version of this
product, us Add/Remove Programs on the Control Panel"
Could anyone offer me some guidance on how to implement upgrades?
Chez,
- Alex
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
