Product, version and build: 5.2.127
32 or 64 bit version of product: 64 bit
Operating system: Windows 7 Pro
32 or 64 bit OS: 64 bit
PowerShell Version: 5.0
The MSI builder works fine, it is the version checking between installed MSI editions that is not correct.
Example:
MyApp.msi build 1.0.1.50 (installed)
Created new build and attempt to deploy:
MyApss.msi build 1.0.1.76
The end result for the upgrade is: The upgrade is not allowed. Another product is already installed.
the workaround:
Bump the version numbers as follows
MyApp.msi build: 1.0.3.76
What is needed:
The Wix Toolset (msi creator) rules need to allow minor build versions as upgrades.
MSI Builder and project version number (for upgrades)
Forum rules
DO NOT POST LICENSE NUMBERS, ACTIVATION KEYS OR ANY OTHER LICENSING INFORMATION IN THIS FORUM.
Only the original author and our tech personnel can reply to a topic that is created in this forum. If you find a topic that relates to an issue you are having, please create a new topic and reference the other in your post.
Any code longer than three lines should be added as code using the 'Select Code' dropdown menu or attached as a file.
DO NOT POST LICENSE NUMBERS, ACTIVATION KEYS OR ANY OTHER LICENSING INFORMATION IN THIS FORUM.
Only the original author and our tech personnel can reply to a topic that is created in this forum. If you find a topic that relates to an issue you are having, please create a new topic and reference the other in your post.
Any code longer than three lines should be added as code using the 'Select Code' dropdown menu or attached as a file.
- gvonpickartz
- Posts: 26
- Last visit: Fri Apr 12, 2024 5:27 am
Re: MSI Builder and project version number (for upgrades)
Unfortunately, there is no way around this. All Windows installers use the first three parts of a version number to update. In other words, it ignores the Revision number.
David
SAPIEN Technologies, Inc.
SAPIEN Technologies, Inc.