search

micro-elements / MicroElements.Swashbuckle.FluentValidation

Use FluentValidation rules instead of ComponentModel attributes
MIT License
380 stars 59 forks source link

Moving to NetStandard 2.1, net6.0 #105

Open petriashev opened 2 years ago

petriashev commented 2 years ago

Many my projects already migrated to netstandard 2.1 or net 6.0. This package supposed to work only in .net core environment so netstandard 2.0 is not needed.

I have plans to migrate it to netstandard 2.1. Any thoughts?

gritcsenko commented 2 years ago

I think that this library should target .NET 6.0 eventually. Targeting .NET Standard 2.x is good but does not allows to use latest C# language version fully. By targeting .NET 6.0 you're showing intended use case.

petriashev commented 2 years ago

.Net 6.0 is too cardinal! I think there can be projects on net3.1 and net5.0. But they can use more old version of course.

petriashev commented 2 years ago

Some thoughts from Immo Landwerth: https://devblogs.microsoft.com/dotnet/the-future-of-net-standard/

gritcsenko commented 2 years ago

.Net 6.0 is too cardinal! I think there can be projects on net3.1 and net5.0. But they can use more old version of course.

.NET 5.0 reached EOS this May and .NET 3.1 will reach EOS this December. I'm personally do not see the point of targeting any of them in the next version of any library.

Some thoughts from Immo Landwerth: devblogs.microsoft.com/dotnet/the-future-of-net-standard

There is another good point in that article that supports idea to move from .NET Standard to .NET:

So, you can think of .NET 5 as .NET Standard vNext.

niemyjski commented 1 year ago

I'd recommend only supporting latest LTS, which will soon be 8. If someone needs an older version they can pay for support or use an older package version.