Future target frameworks about wecantspell.hunspell HOT 7 CLOSED

I totally agree with what you've already said. I can only speak from the perspective of what I need and for sure netstandard 2.0 is a must for me. Then, thinking about the future of the library itself, it's clear that the future of .NET lies on the new .NET 6.0 and its future iterations, with both .NET Core and Framework slowly fading into past. It means that for sure net 6.0 must be supported. Plus, netstandard 2.0 will be able to carry most of the updates onto net framework while it lasts.

from wecantspell.hunspell.

net6.0;netstandard2.0 for the win!

from wecantspell.hunspell.

As the nerds say, "This is the way." This change is applied to the refactoring branch, which will Soon make it's way to the 4.0 release branch.

from wecantspell.hunspell.

Sure, working on a spellchecking library on a Friday night while getting drunk on carbonated water is totally fun, but is spell checking fun enough to put in a game? Apparently it is! I don't know much about Unity but it sounds like both the net4.x and netstandard options support a netstandard2.0 target, so I think that will be a required target in 4.x . Also, it's probably the most "portable" option right now for most software out there.

from wecantspell.hunspell.

Looking over Microsoft's support schedule as well as looking at some quickly compiled data based on nuget usages, here is what I'm thinking for target frameworks:

For .NET "Core":
net6.0, net5.0, and netcoreapp3.1 should all be supported for at least a few months. net6 will be the only one of the three to see support past 2022 though. I think that makes net6.0 an important explicit target and will probably be good enough to work with net7.0 applications.

For full framework:

It appears that nobody is really using net45 anymore and for the one person out there, I don't plan on removing the 3.x releases from nuget, so that should still work. I figure if somebody is worried about updates, they wouldn't still be on net45. That isn't so say I'm definitely dropping the net45 target, but I may drop it if it becomes a massive pain for me. Already, the lowest target that VS2022 seems to support out of the box is net451 so, it might help with contributions to drop support for net45. I think this being a spell check library means that nobody will want to contribute anyway though, so maybe that doesn't matter 🤷‍♂️. Ultimately, most usages seem to be net47+ with a smaller group around net461. Considering that everything below net462 will lose support by 2023, maybe net462 is a good candidate for the minimum full framework version.

Net standard:

Netstandard2.0 is just too important, it has to be included. This should also bring unity compatibility with it, along with other full framework support cases too. Considering the popularity of the soon to be derprecated netcoreapp3.1, and it's standard 2.0 compatibility, I think it would be good to drop netstandard1.3 and keep 2.0 .

Microsoft support schedule: https://dotnet.microsoft.com/en-us/platform/support/policy/dotnet-core

from wecantspell.hunspell.

My current thinking for future targets is going to be net6.0;netstandard2.0 for a 4.x release with an intent to support net462 through netstandard2.0 . If anybody has good reasons for keeping net45 around, I'll hear them, but I would love to drop it going forward.

from wecantspell.hunspell.

@Tigrisor, @funex, and @ACCIAI0: do any of you have opinions on target frameworks?

from wecantspell.hunspell.