Fallback to AssemblyVersion if InformalVersion is NullOrEmpty
#2705
Conversation
This file contains 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
bruno-garcia
approved these changes
Oct 6, 2023
vaind
pushed a commit
that referenced
this pull request
Oct 14, 2023
This was referenced Nov 16, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Resolves #2664
This removed the comments and todo.
Based on this comment: #1538 (comment) the
AssemblyInformationalVersionAttributeis automatically created and defaults to<Version>.This can be disabled with the
GenerateAssemblyInformationalVersionAttributeleading to the informal version returningnull.In that case, the SDK falls back to the assembly version.
#skip-changelog