Follow up to Support for CRC-64/NVME

[normj]

Following up on the thread about the new support adding in System.IO.Hashing that will support our needs for CRC-64/NVME and CRC-64C. I was able to integrate the .NET 11 preview 3 version of System.IO.Hashing in the AWS .NET and use it for checksums to S3. Thanks for adding the support.

I am getting the compiler warning that this hasn't been tested on .NET 8 the currently latest target for the AWS SDK we build for. I was hoping this being in a .NET Standard 2.0 project I would be good. My rough thinking is we do a minor version bump of the SDK in November to switch to this. At that point the build targets for the SDK would be:
.NET Framework 4.7.2
.NET Standard 2.0 (We need this for PowerShell)
.NET 8
.NET 11

By the time the new System.IO.Hashing ships will I be safely able to use the new work across these targets? That would be the best and I can drop a native dependency library we use as the bandaid today. The fallback would be to use it only for .NET 11, that would be sad because the .NET Framework and .NET Standard 2.0 targets are not going away anytime soon.

@jeffhandley @bartonjs

[jeffhandley]

Thanks a bunch, @normj! .NET 8 and .NET 9 will both hit end-of-life in November when .NET 11 is released (putting only .NET 10 and .NET 11 in support at that time), but I'll defer to @bartonjs on whether netstandard is a possibility here.

[normj]

Understand about .NET 8 and 9 being end of life. We generally let you guys encourage the community to move off end of life versions but don't remove build targets till our metrics show the usage has hit some minimum bar.

I guess what I'm hoping since the code is in a .NET Standard 2.0 package that it would be valid to use in any target that supported .NET Standard 2.0.

Just in case it isn't clear I am grateful for the added support and we will use it no matter what. I'm just trying to understand if I can remove all of our legacy stuff we do.