Hey all,
I build a lot of installers for my project. In an attempt to make it easy
for users to install a newer version over an existing installation, I've
been doing this:
<?define InstallVersion = "X.0.0" ?>
<?define RTMInstallVersion = "1.0.0" ?>
....
<Upgrade Id='$(var.UpgradeID)'>
<UpgradeVersion Minimum='$(var.InstallVersion)' IncludeMinimum='yes'
OnlyDetect='yes' Language='1033' Property='NEWERPRODUCTFOUND' />
<UpgradeVersion Minimum='$(var.RTMInstallVersion)'
IncludeMinimum='yes' Maximum='$(var.InstallVersion)' IncludeMaximum='no'
Language='1033' Property='UPGRADEFOUND' />
</Upgrade>
Every time I do a build I bump the InstallVersion "X" up one. It's
obviously a hack, but has been working well. At least until now, when my
InstallVersion hit "128.0.0" and my build immediately started complaining
about an ICE61 error: "Upgrade.VersionMax cannot be less than
Upgrade.VersionMin. (UPGRADEFOUND)"
I'm not entirely sure what's going on here, but my compile works if I set
InstallVersion to 127.0.0 and fails if I use 128.0.0. But more generally:
there must be a better way to handle upgrades, or am I just being too
liberal with the major version number?
Colin
<wix-users@lists.sourceforge.net>
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
