-
Notifications
You must be signed in to change notification settings - Fork 46
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
Follow MS Versioning Guidance on Assembly Versions #61
Comments
WalkerCodeRanger
added a commit
that referenced
this issue
Dec 30, 2020
WalkerCodeRanger
added a commit
that referenced
this issue
Dec 30, 2020
WalkerCodeRanger
added a commit
that referenced
this issue
Dec 30, 2020
WalkerCodeRanger
added a commit
that referenced
this issue
Dec 30, 2020
WalkerCodeRanger
added a commit
that referenced
this issue
Dec 30, 2020
WalkerCodeRanger
added a commit
that referenced
this issue
Dec 30, 2020
WalkerCodeRanger
added a commit
that referenced
this issue
Dec 30, 2020
Because packages with assembly versions of |
This has been done, but it is being left open to verify when publishing the v2.1.0 release |
Verified in v2.1.0 release package |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The open-source library guidance on versioning suggests using only the major version in the assembly version. This appears to have been done for some of the previous assembly versions. When the build was redone, it was set up to match the assembly version to the package version.
The text was updated successfully, but these errors were encountered: