-
Notifications
You must be signed in to change notification settings - Fork 11
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
Remove AssemblyVersion pinned constraint for .NET Standard #160
Remove AssemblyVersion pinned constraint for .NET Standard #160
Conversation
Looking at the errors. |
13230a8
to
2cf036a
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You had already mentioned offline that you intended to reduce this PR to just System.Memory and System.Threading.Tasks.Extensions. I confirmed that through inspecting assemblies in packages and ref packs. I added a couple more comments around things that we might want to consider for System.Buffers
and System.Numerics.Vectors
. Looks like those two were different because of the reference assemblies that they used to ship.
src/System.Reflection.DispatchProxy/src/System.Reflection.DispatchProxy.csproj
Outdated
Show resolved
Hide resolved
src/System.Runtime.CompilerServices.Unsafe/src/System.Runtime.CompilerServices.Unsafe.ilproj
Outdated
Show resolved
Hide resolved
src/System.Threading.Tasks.Extensions/src/System.Threading.Tasks.Extensions.csproj
Outdated
Show resolved
Hide resolved
In general, if a previously frozen AssemblyVersion property isn't frozen anymore, please move it into the PropertyGroup that contains all the moving versions. And put the properties with the same name together. |
Fixes #159
We need to make sure that the AssemblyVersion for the netstandard2.0 DLLs of the new packages is greater than the AssemblyVersion for the netstandard2.0 DLLs of the last released packages in nuget.org, similar to what we've been doing for .NET Framework AssemblyVersions.
For some of these cases we need to be mindful of keeping the new netstandard2.0 AssemblyVersion under the AssemblyVersion of the last released netcoreappX.X version.
I collected all the numbers before and after:
System.Buffers
C:\Program Files\dotnet (netcoreapp2.1):
nuget.org (netstandard2.0):
main (netstandard2.0):
This PR (netstandard2.0):
System.Memory
C:\Program Files\dotnet (netcoreapp2.1):
nuget.org (netstandard2.0):
main (netstandard2.0):
This PR (netstandard2.0):
System.Numerics.Vectors
C:\Program Files\dotnet (netcoreapp2.1):
nuget.org (netstandard2.0):
main (netstandard2.0):
This PR (netstandard2.0):
System.Runtime.CompilerServices.Unsafe
C:\Program Files\dotnet (net6.0):
nuget.org (netstandard2.0):
main (netstandard2.0):
This PR (netstandard2.0):
System.Threading.Tasks.Extensions
C:\Program Files\dotnet (netcoreapp2.1):
nuget.org (netstandard2.0):
main (netstandard2.0):
This PR (netstandard2.0):
System.Reflection.DispatchProxy
C:\Program Files\dotnet (netcoreapp3.1):
nuget.org (netstandard2.0):
main (netstandard2.0):
This PR (netstandard2.0):
System.Data.SqlClient
This assembly does not need the change.