robinrodricks
[Question] .Net 6 has reached the end of its lifecycle. What about add .Net 8 and .Net 9 to `TargetFrameworks`?
Ref: https://dotnet.microsoft.com/en-us/download/dotnet/6.0
This release has reached end of life, meaning it is no longer supported. We recommend moving to a supported release, such as .NET 9.0. See our support policy for more details.
https://github.com/robinrodricks/FluentStorage/blob/15d9ff92bea5570c4e6406db0aa5b5484a43a895/FluentStorage/FluentStorage.csproj#L4
See also: https://learn.microsoft.com/en-us/dotnet/standard/frameworks#latest-versions
Suggestion
<TargetFrameworks>netstandard2.0;netstandard2.1;net6.0;net7.0;net8.0;net9.0</TargetFrameworks>
.NET 6 libs can be used in .NET 9 without any issues.
Correct, however, cross-compiling can light up performance improvements without any source changes; for example, compiling for net8 and net9 will target faster APIs for strings in certain cases (due to the preferred overload resolution to ReadOnlySpan<>).
Support for older versions may be kept for reliability reasons, but currently supported TFMs should always be included in the list of compiled targets.
For most of my libraries, I support every LTS TFM that I have ever released support for, as well as all currently supported TFMs. This means, for one of my libraries, netstandard2.0, net6.0, net8.0, and net9.0.
Yes great idea, but every time we add a new target, the DLL and thus Nuget size increases.
Yes great idea, but every time we add a new target, the DLL and thus Nuget size increases.
So maybe LTS with latest STS only?