Change version strategy in V4 to set AssemblyVersion #3335
Merged
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.
V3 we always set the
AssemblyVersion
because the version number is part of the assembly identity. If you change the version number any assemblies that depend on have to recompile for the new version. This strategy dated back to when the SDK only targeted .NET Framework.In .NET Core the version number is not part of the assembly identity so users are not required to recompile. This PR changes the strategy for .NET Core set the
AssemblyVersion
to the same value ofAssemblyFileVersion
. For the .NET Framework targets we continue to use the same strategy.Example of a generated `AssemblyInfo.cs