-
Notifications
You must be signed in to change notification settings - Fork 5
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
Supporting .NET 6 #106
Comments
Since .NET 6 is coming out this fall which is LTS, I would suggest to rename it to be .NET 6 compatible. What do you think? |
.NET 6 released. 🎉 |
From @fgheysels: Since .NET 6 has been released, and .NET 6 is the latest LTS version, we should start supporting templates that are based on .NET 6. I don't know if we should still support .NET Core 3.1 as well ? Maybe default to .NET 6 and provide a parameter to generate a project for .NET Core 3.1 ? Although this will be something that we'll only support for a short term as .NET Core 3.1 support ends in december 2022. |
My idea would be (for Arcus libraries):
For templates:
|
Definitely the templates to .NET 6, I think that's logical as it's new projects. The other thing, we'll have to check. |
I've changed my mind regarding Arcus libraries: We're currently targetting .netstandard2.0 and .NET Core 3.x. Priorities for me would be:
Any thoughts @stijnmoreels @tomkerkhove @gverstraete @pim-simons |
I haven't had too much time to look into this, but the way you describe it @fgheysels it seems like a good plan 👍🏻 I am interested in why you changed your mind regarding .net standard, not saying I don't agree, just interested in the thought process behind it 😄 |
I agree, (discussed offline). We should check if we don't break anything in the process. Technically (very technically), this migration from netstandard 2 > 2.1, is maybe something that is considered a breaking change... |
https://devblogs.microsoft.com/dotnet/announcing-net-standard-2-1/ |
Hmm, seems like remaining on netstandard 2.0 is the way to go then (for libraries that already had this). There are, however, libraries that target both (netstandard 2.0 & netcoreapp 3.1). |
We could also say that we'll stop supporting .NET Framework in the near future. |
We could, but I don't know what's the common target framework for Codit projects (existing and new)? Maybe some environments require one or the other... |
Only supported versions by Microsoft at the moment is .NET Core 3.1, .NET 5 & 6. I think we can raise the bar to that minimum requirement no issue: https://dotnet.microsoft.com/platform/support/policy/dotnet-core If new projects are started with older versions, I think we need to have a discussion with them ;) |
Agreed |
Do we have an overview of which projects still need to be migrated, or for which projects we haven't released a .NET 6 version yet ? I thought we had an issue where we kept track of that, but i can't find it anymore. |
It's referenced in the issue's description: #188 will make sure of this. |
Ah ok. :') |
Yes, of course. Like we talked about: .NET 6 support is our primary objective, service-to-service correlation closely behind that one. The next library is background jobs, so that's the one I was focusing on the last couple of days/weeks. |
Don't want to put pressure, but any ETA? |
😄 that's hard to say. The current focus is background jobs, but that is also the last big repo with functionality, then it's just updating our templates which could go quite fast. |
@gverstraete : The .NET 6 version of BackgroundJobs is released. :) |
Ok, this is officially done! 🥳 |
Is your feature related to a problem? Please describe.
We should support .NET 6 throughout all the Arcus repositories, as .NET Core will vanish the end of the year (2022).
What suggestion do you propose?
#188 will make sure that we support the lowest possible version for the target framework.
Additional context.
Original remark:
The text was updated successfully, but these errors were encountered: