-
Notifications
You must be signed in to change notification settings - Fork 36
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
Choice of .Net Standard 1.0 vs 1.1 #15
Comments
Why does it matter at this point, what are you trying to do? |
Seing how long the previous version of framework got to live in this project it would make sence to implement as high a level as possible because it might take 10 years again before the next time. |
.NET Framework 4.5.2, which is the lowest supported version of .NET Framework, supports .NET Standard 1.2. .NET 4.5 and 4.5.1 have been out of support for a long time and should not be run in production... |
That is correct but currently the netstandard branch builds for .Net Framework 4.0 and .Net Standard 1.0, 1.3 & 2.0 |
.NET Framework 4.0 is not supported anymore either. I will not actively support unsupported .NET Framework versions, sorry. The current package supports all supported versions of the .NET on all platforms. |
I am not saying what you are supporting, but what you are building for |
Sorry, I misunderstood. At this point, there's no need to target anything else as this release is based purely on the upstream. I won't accept changes that are specifically to this repo, any changes need to be made in the BC repo. What platforms they target is their choice. |
But this is the csproj file made specifically for the netstandard build so only in that branch. |
Closing as no platform that's < NET Standard 2.0 is supported by Microsoft and there's a .NET 4 target as well. |
Seing the implemented versions of .Net Standard 1.0 and 1.1 there is no difference:
https://docs.microsoft.com/en-us/dotnet/standard/net-standard
So you could change .Net Standard 1.0 to 1.1 without any compability issues.
The text was updated successfully, but these errors were encountered: