Wix is allowing me to create msi files with a large number in the fourth
version index (6-digit numbers, i.e. 11).
I'm trying to use burn to create a bootstrapper which bundles my wix
installer. When I include an msi in the bundle which has a fourth version
index greater than 65535 (16-bit
This is expected behavior because all of WiX ignores the 4th version
number... If you want to test for it, you must do it manually.
Carter
Quoting Ed ecarp...@gmail.com:
Wix is allowing me to create msi files with a large number in the fourth
version index (6-digit numbers, i.e. 11).
We are okay with WiX ignoring this number for upgrading purposes. We simply
attach the build CL in the 4th index so we can trace each MSI back to the
point of creation if needed
The problem seems to be that Burn can't parse MSI files which fill this
value with a number larger than 16-bit
Your getting the error because the number is ignored all together,
regardless of type, int long string doesnt matter... its unable to
parse because there is no underlying code in burn that says parse 4th
digit
Quoting Ed ecarp...@gmail.com:
We are okay with WiX ignoring this number for
Sorry I'm still a bit confused. If this is the case, then why am I able to
create a bootstrapper which bundles an MSI file that has a fourth index
version number of 65535?
The fact that an MSI with fourth index 65535 (1.0.0.65535) will execute
from a WiX bootstrapper with no issue, while an MSI
See this post:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Setup-upgrade-needs-to-care-for-4th-part-of-version-number-td3250189.html
Carter
Quoting Ed ecarp...@gmail.com:
Sorry I'm still a bit confused. If this is the case, then why am I able to
create a bootstrapper which
On 6/9/2014 5:32 PM, Ed wrote:
Wix is allowing me to create msi files with a large number in the fourth
version index (6-digit numbers, i.e. 11).
How are you authoring that? If you put such a version as a literal
string, the compiler will fail with an error message saying you can't do
On 6/9/2014 6:01 PM, Carter Young wrote:
Your getting the error because the number is ignored all together,
regardless of type, int long string doesnt matter... its unable to
parse because there is no underlying code in burn that says parse 4th
digit
Burn supports all four places of version
My Mistake, it's the MSI causing the issue, not the Burn Engine. See
the post I linked earlier...
Quoting Bob Arnson b...@joyofsetup.com:
On 6/9/2014 6:01 PM, Carter Young wrote:
Your getting the error because the number is ignored all together,
regardless of type, int long string doesnt
Thank you Bob,
I have isolated the issue by using basic Visual Studio WiX projects (Setup
Project and Bootstrapper Project)
To create the MSI, I created a simple Setup Project and changed the
Product's Version attribute to 1.0.0.65536. Then I crated a basic
Bootstrapper Project and added a
concerning 'Invalid product version '{0}'. Product version must have a
major version
less than 256, a minor version less than 256, and a build version less
than 65536.' I believe the version format is Major.Minor.Build.Revision,
hence the compile error is correct, albeit missing any limit
On 6/9/2014 6:51 PM, Ed wrote:
I understand the build version must be less than 65536, but I believe that
refers to the third index in the version number.
Product versions must be less than or equal to 255.255.65535.65535.
http://msdn.microsoft.com/en-us/library/aa370859%28v=vs.85%29.aspx makes
I see, thanks for the help!
Our team has been filling that fourth index with larger numbers for years
with no ill affects, so I assumed this was acceptable. I will deliver to
them the bad news ;)
I will also open a bug for wix to flag such builds with compile warnings so
other teams don't
Defect added: http://wixtoolset.org/issues/4443/
On Mon, Jun 9, 2014 at 4:27 PM, Ed ecarp...@gmail.com wrote:
I see, thanks for the help!
Our team has been filling that fourth index with larger numbers for years
with no ill affects, so I assumed this was acceptable. I will deliver to
them
14 matches
Mail list logo
