Replies: 1 comment 5 replies
-
|
With .netstandard, we still have some .NET Core support. I think that was also the reason why we still include this. But, as I recall, .NET Core will be deprecated end of this year, so it's indeed not a very long timespan or added-value that it would have. We could consider moving directly to .NET 6, bc the Arcus libraries will otherwise have two major 'breaking changes' (.NET Core > .NET standard, .NET standard > .NET 6). And it takes quite some work to migrate every repo, and dependent repo towards this. |
Beta Was this translation helpful? Give feedback.
5 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
We're currently supporting (or moving to supporting) .NET Core 3.x, .NET 6 and .NET Standard 2.1 in all our Arcus projects.
I wonder if we should explicitly still support .netstandard 2.1.
If we look at this overview, it seems like supporting .netstandard 2.1 next to .NET 6 / .NET Core doesn't really make much sense, or am I mistaken ?
By migrating from .netstandard2.0 to .netstandard2.1, we no longer support .NET Framework.
Question that remains: will we support mono & Xamarin ?
Some additional reading
https://devblogs.microsoft.com/dotnet/the-future-of-net-standard/#what-you-should-target
Any ideas @stijnmoreels @pim-simons @ALaks96 @gverstraete ?
Beta Was this translation helpful? Give feedback.
All reactions