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
LGHT0001: Version string portion was too short or too long. (3.9 stable) #4589
Comments
Please copy the .pdb files from https://wix.codeplex.com/downloads/get/925663 next to your WiX binaries and paste the full stack trace here. That should tell us whether a workaround is possible.
|
I hope I'm doing something wrong. I'm not seeing a stack trace in the VS windows or in an external file in the project outputs. I've copied the PDBs from the link provided in with the existing 3.9 install, verified I have light.pdb next to light.exe, opened VS and rebuilt the project. Should I be looking somewhere I'm not currently examining for the desired stack trace? The relevant section of the output window: 17>------ Rebuild All started: Project: MyProduct.Configuration.Complete, Configuration: Debug x86 ------
|
Hmm...I think it's the VS output window. Try running at the command line. For example, here's my typical MSBuild alias:
|
I tried the checkbox for verbose output in the project property in VS, but that didn't help. Just a note in case that saves anyone else some trouble/time. Building from the command line with your parameters generated a msbuild.log file with the stack trace! Thanks for providing that hint. Now, for the hopefully helpful stack trace:
|
Thanks. Unfortunately, I don't think there's a workaround...I can't say I've ever seen someone trying to use a five-part version number, hence the exception instead of useful error. MSI ignores the fourth (and any other) version parts so upgrades won't work well.
|
Thanks for trying, I appreciate the support. The 5 place version number was a first for me too. Digging in the MSI, there is evidence to suggest that the version of InstallShield that may have generated the package does not prevent this from happening. ;) Even if I'm stuck without a workaround, I hope we can get a little more information out from Light so there isn't a hunt for the responsible package should this impact anyone else. Thanks again for trying to find a workaround!
|
Best-effort recovery of MSI three-part version numbers with a warning if there's anything beyond.
|
|
|
When testing the 3.9 stable release, I am encountering a new issue that is not happening in my production environment using the 3.8 stable release. Building a Burn project, I receive the error: "LGHT0001: Version string portion was too short or too long." The entry in the error list only points to the burn project, line 0 column 1. After running through and commenting out lines until the build succeeded, I identified an MSI that is delivered to me which has an invalid ProductVersion property of "1.0.0.0.001" (5 sections instead of 4).
I'm certainly not against the validation. Unfortunately for me, modifying the original MSI would break the digital signature and is not acceptable, nor is rebuilding the MSI by my team.
Could there be an attribute added to the MsiPackage to provide an alternate version number?
Could Light provide a little more information about which package caused the failure?
Any other suggestions?
Thanks.
The text was updated successfully, but these errors were encountered: