issue #2887 set release number in assembly version AssemblyVersion #2888
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
…sion to avoid version mismatch with dlls in GAC
|
This problem is breaking our code deployment. Is it possible to get this merged and released at some point soon @JamesNK ? |
|
Not updating the assembly version every release is an intentional decision to reduce problems around binding redirects. Newtonsoft.Json has had this behavior for years. |
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.
AssemblyVersion should always be unique specified for each release.
This is necessary to avoid version mismatch with dlls in GAC
See AssemblyVersion only contains Major version causes DLL conflicts #2887