Fix of issue with ApiVersions that do not contain a Build or Revision number #53
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… number The DefaultAttributeControllerVersionDetector throws a ArgumentOutOfRange exception on line 18 when the ApiVersionAttribute is used with only a Major / Minor, or used with Major / Minor / Build. The reason is the use of the default -1 value for BuildNumber / RevisionNumber in the System.Version constructor.
|
I've seen your contribution - let me take some time to look at it. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The DefaultAttributeControllerVersionDetector throws an ArgumentOutOfRange exception on line 18 when the ApiVersionAttribute is used with only a Major / Minor, or used with Major / Minor / Build. The reason is the use of the default -1 value for BuildNumber / RevisionNumber in the System.Version constructor.