Drop .NET Framework/Net Standard/(Net Core 6?) Support

[micah686]

@alxnull
What do you think about dropping .NET Framework Support for this library (or at least mark the current version as the last version to support .NET framework)
It was mentioned in this Issue: #60
I do think it would be good to drop support for it. People that still need framework support can still download a version from nuget that has support for .net framework/net standard. However, it would allow the library going forward to focus on .net 6/8/9/10... support, which has been adding a lot more cross platform support, use more efficient operations, such as some File Read/Write that is much faster on latest net core/C# versions.

If we did do a hard break over, it would also allow us to do some refactoring of the functions, models, and logic, as it could be considered a major feature upgrade, and therefore have breaking changes that you wouldn't normally want to have in your library, for fear of breaking people's workflows using the current version.

I know I would like to rework the whole binary downloader tools, but I don't want to make too many significant changes in case if someone is using those methods.

I think if we switched over to just net core 8.0 and above (while I would have liked to include .net 6, File.SetUnixFileMode isn't available on net 6), it would allow for easier development, as we would no longer be held back by the legacy .NET (framework/standard) versions, and we could focus on using the latest feature sets that dotnet offers.

We could ass a section at the top of the readme to mention which is the last tagged version to support the legacy .NET versions. That way, someone who still needs it can find the old version without much of an issue.

[alxnull]

Hey @micah686,

sorry for the very late response and thanks for this suggestion!
Your reasoning sounds perfectly sensible to me and I agree we could drop legacy .NET Framework and .NET Standard in upcoming major releases and focus on >= .NET 8.0 going forward. If done together with further breaking changes, we could e.g. release a 2.0 that's optimized for newer .NET, while keeping 1.x versions with .NET Framework/ .NET Standard support.

Unfortunately, I don't have much capacity to maintain this library these days (as you probably have realized by now), so any progress from my side will be slow. But I would very much welcome any of your contributions to these changes! Happy to discuss any further changes you have in mind related to optimizing for newer .NET.

(Also open to adding you as a collaborator to this library in case you are interested in continuing to contribute.)