Hello All,
due to political issues (see below) my setups need to be able to upgrade
when only the 4th part of the version info changes.
Example: V1.0.0.1 needs to upgrade V1.0.0.0. My installers always do major
upgrades, the product GUI always changes (that is OK and not an issue to
discuss).
I had a similar problem the way I got round it was to set the upgrade code to
include the maximum version, e.g. UpgradeVersion/@IncludeMaximum=yes. This
will generate an ICE61 which you will need to ignore. This isn't perfect as
1.2.3.4 will be downgraded by 1.2.3.3 but if you are sure two
Hello Neil,
thank you - I didn't find this one. It is not perfect, but sufficiently good
:-). If someone can tell me the perfect solution, I'm still open to it.
Thanks again!
Dirk
On Mon, Jul 13, 2009 at 12:00, Neil Sleightholm n...@x2systems.com wrote:
I had a similar problem the way I got
The perfect solution would be for Windows Installer to understand 4 part
version numbers like every other system on the planet :-)
One other point, I schedule RemoveExistingProducts after InstallValidate, it
gets a bit more messy if this is not the case.
Neil
Neil Sleightholm
X2 Systems
4 matches
Mail list logo