The product out there (and it has had many releases) did not set
upgrade code but used a registry key in the past. So, do I not have a
situation where UpgradeVersion tags would fail if I suddenly introduce
them, and where I need to keep the old scheme
in parallel?
Specific about this product is th
MSI sees 1.2.3.10 and 1.2.3.9 as 1.2.3 - so they appear as the same
version. In order to prevent a downgrade on a 4th field change, you
can rely on the (documented) fact that MSI ignores the 4th field to
prevent installs where the version numbers are identical to Windows
Installer.
I use the follo
The solution in the tutorial is fine. It's the way that "everybody" detects
versions based on UpgradeCode, old and new to prevent downgrades and perform
upgrades.
You have a problem in that the 4th digit of the ProductVersion isn't used
anyway in major upgrades, so your upgrades will require y
3 matches
Mail list logo