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

WIXBUG:4589 #195

Merged
merged 1 commit into from
Jan 31, 2015
Merged

WIXBUG:4589 #195

merged 1 commit into from
Jan 31, 2015

Conversation

barnson
Copy link
Member

@barnson barnson commented Jan 31, 2015

Catch exceptions from Version when passing in arbitrary strings. For bundles, try to recover a three-part version number.

… strings. For bundles, try to recover a three-part version number.
robmen added a commit that referenced this pull request Jan 31, 2015
@robmen robmen merged commit f72de47 into wixtoolset:develop Jan 31, 2015
@@ -611,7 +611,23 @@ private void ResolveMsiPackage(BinderFileManager fileManager, Dictionary<string,

if (!Common.IsValidModuleOrBundleVersion(this.Version))
{
this.core.OnMessage(WixErrors.InvalidProductVersion(this.PackagePayload.SourceLineNumbers, this.Version, sourcePath));
// not a proper .NET version (i.e., five fields); can we get a valid three-part version number?
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we try to get a four-part version number before falling back to three? Burn does use the fourth part.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we have the technology for that...but the bug says three. Why does the bug say three? We should fire the scribe. I can't think of a reason not to take all four parts except that major upgrades aren't going to work either way...

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't follow your comment about major upgrades. Burn will consider 1.0.0.0 to 1.0.0.1 a major upgrade assuming a standard Upgrade table.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants