[wix-users] Failed to convert version when upgrading previous Installshield install

[Dennis Costello]

Thanks for the input.  I have read both of these when I first ran into this problem but there isn't a fix for how to handle this problem.  The Burn engine fails to run the msi when the detected status is unknown.  I need to know how to either change that status in the custom ba or what I need to do to force that msi to run if that status is unknown.

This is only an issue when trying to run the msi from the bundle.

Thank you!


-----Original Message-----
From: wix-users [mailto:wix-users-bounces at lists.wixtoolset.org] On Behalf Of Tobias S
Sent: Wednesday, June 21, 2017 9:12 AM
To: WiX Toolset Users Mailing List <wix-users at lists.wixtoolset.org>
Subject: Re: [wix-users] Failed to convert version when upgrading previous Installshield install

when googling for "0x8002000a: Failed to convert version: to DWORD64 for ProductCode" this heads to several issues with wrong version numbers.
Consider e.g. https://github.com/dotnet/cli/issues/1473 for better understanding and always try to stick to the versioning as described in https://msdn.microsoft.com/en-us/library/windows/desktop/aa370859%28v=vs.85%29.aspx
. Consider correct versioning as highest importance when using Windows Installer. Also consider "outside" versioning and "inside" versioning can be different ("Outside" versioning the things the customer sees like e.g.
ProductName:MyProduct 2018 - "Inside" versioning things only developers see like e.g. in that case 18.xxx.xxxxx)

InstallShield doesn't care about correct versions unfortunately. We also had to fight with issues when using minor versions higher than the allowed 255.

For the issue: Not sure whether this might be fixed in newer wix builds.
Maybe try that. Otherwise think possible maybe by custom BA.

____________________________________________________________________
WiX Toolset Users Mailing List provided by FireGiant http://www.firegiant.com/