Dotnet version changes

[JoeSchulte]

By changing the project to target net9.0 instead of netstandard2.0 I cannot use the latest version with my .Net 8.0 project. Seems like it would be good to keep the libraries targeting netstandard2.0 to keep the usability as broad as possible. Another option would be to target multiple versions, but that is a little more complex. Even going to 2.1 limits this from being used in older 4.8 Framework applications.

[HakanL]

My bad, I upgraded my main consumer project to .NET9 so I just upgraded everything. I can't target anything less than .NET8 without a lot of work since I'm using high-performance stuff like ReadOnlyMemory and it doesn't seem to be available even in .NET Standard 2.1, so this project will most likely have to be .NET8 or higher.

[HakanL]

New Nuget building now, please let me know if it will work with .NET8

[JoeSchulte]

If you are making code changes that require a newer version of .Net then maybe you could at least limit to the last LTS version. I didn't see any code changes in Master, but maybe you are working on those in a branch.

[HakanL]

Yeah, you're right, to be honest I built this project primarily for my own use-case and I forget there are other users of this package (few, but still). Sorry about that. I switched to main branch. It should be in Nuget now, version 2.0.31.