Skip to content
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

Update target frameworks #304

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

0xced
Copy link
Contributor

@0xced 0xced commented Oct 5, 2023

.NET Core 3.1, .NET 5.0 and .NET Framework 4.6.1 are all out of support now

Replace them with .NET 6 (LTS) which will be supported until November 12, 2024 and .NET Framework 4.6.2 which will be supported until Jan 12, 2027

Also drop .NET Standard 2.1 in favor of .NET 6.0 in the Ductus.FluentDocker project. The additional .NET Standard 2.1 target framework was not bringing anything substantial over .NET Standard 2.0. The .NET 6.0 at least will be beneficial for string interpolation. See also Are there benefits in producing a .NET 6.0 version of a .NET Standard 2.0 library? on Stack Overflow.

.NET Core 3.1, .NET 5.0 and .NET Framework 4.6.1 are all out of support now

Replace them with .NET 6 (LTS) which will be supported [until November 12, 2024][1] and .NET Framework 4.6.2 which will be supported [until Jan 12, 2027][2]

Also drop .NET Standard 2.1 in favor of .NET 6.0 in the `Ductus.FluentDocker` project. The additional .NET Standard 2.1 target framework was not bringing anything substantial over .NET Standard 2.0. The .NET 6.0 at least will be beneficial for [string interpolation][3]. See also [Are there benefits in producing a .NET 6.0 version of a .NET Standard 2.0 library?][4] on Stack Overflow.

[1]: https://dotnet.microsoft.com/en-us/platform/support/policy/dotnet-core#lifecycle
[2]: https://learn.microsoft.com/en-us/lifecycle/products/microsoft-net-framework
[3]: https://devblogs.microsoft.com/dotnet/performance-improvements-in-net-6/#arrays-strings-spans
[4]: https://stackoverflow.com/questions/70778797/are-there-benefits-in-producing-a-net-6-0-version-of-a-net-standard-2-0-librar/72266562#72266562
@mariotoffia
Copy link
Owner

Thanks! :) - I'm merging when I get rid of gitversioning.tool and migrated from appveyor to GH workflows. I'll try to do it before end of October.

Cheers,
Mario

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants