Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ParseTypeLibElement MinorVersion maximum value check #4726

Closed
wixbot opened this issue Mar 26, 2015 · 7 comments · Fixed by wixtoolset/wix#24
Closed

ParseTypeLibElement MinorVersion maximum value check #4726

wixbot opened this issue Mar 26, 2015 · 7 comments · Fixed by wixtoolset/wix#24
Assignees
Milestone

Comments

@wixbot
Copy link

wixbot commented Mar 26, 2015

Hi,

I noticed in ParseTypeLibElement, WIX uses byte.MaxValue to check the range, however from Microsoft, minor version can be a 16bit value which is the same as MajorVersion

minor-value
Specifies a short unsigned integer between zero and 65,535

I assume it needs to be changed to ushort.MaxValue?

https://msdn.microsoft.com/en-us/library/windows/desktop/aa367306(v=vs.85).aspx

minorVersion = this.core.GetAttributeIntegerValue(sourceLineNumbers, attrib, 0, byte.MaxValue);

Thanks
Jim

Originally opened by jim

@wixbot
Copy link
Author

wixbot commented Mar 31, 2015

AssignedTo set to bobarnson
Release changed from v3.9 to v3.10

@wixbot
Copy link
Author

wixbot commented Apr 20, 2015

https://msdn.microsoft.com/en-us/library/aa372092%28v=vs.85%29.aspx says

Version

This is the version of the library. The major and minor versions are encoded in the four byte integer value. The minor version is in the lower eight bits. The major version is in the middle sixteen bits.

which explains the current implementation.

Recommend wontfix.

Originally posted by barnson
Status changed from Open to Untriaged

@wixbot
Copy link
Author

wixbot commented Apr 21, 2015

Non-advertised should support 16-bit range. Advertised cannot.

Release changed from v3.10 to v4.0

@wixbot wixbot added this to the v4.0 milestone Dec 20, 2015
@cpuwzd
Copy link

cpuwzd commented May 23, 2021

I'm looking at this issue. I think I can fix the bug, but I don't know where to put failing test(s) for Compiler.Package or Compiler.
If I need to build new structure, what would the fixture be named and where would the file fit in the hierarchy?

Ron

@robmen
Copy link
Member

robmen commented May 23, 2021

@robmen robmen assigned cpuwzd and unassigned barnson May 23, 2021
@barnson barnson self-assigned this Jun 10, 2021
@barnson
Copy link
Member

barnson commented Jun 10, 2021

I'll take a look at your pull request.

@cpuwzd
Copy link

cpuwzd commented Jun 10, 2021 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
No open projects
Development

Successfully merging a pull request may close this issue.

4 participants