At this time, .NET 4,8, .NET Core 3.1 and .NET 6 are currently supported LTS releases. We want to run the unit tests, integration tests and benchmarks only against those frameworks.
Running tests & benchmarks on obsolete TFMs is causing a burden for maintenance since they're no longer available with new VS2022 installs and on the build agents. And I am fairly confident that as long as we target .NET Standard 2.0 and run our tests against those three current LTS releases the library will work on for example .NET Core 2.1 too.
FYI: At some point in the the past we specifically ran tests against .NET 4.6.1/4.6.2 too because of the broken .NET Standard support in there. Those versions are now ancient (8 years) and we're not spending any effort on verifying the lib still works on those old TFMs anymore. You can be fairly certain that version 5.0.0 works on .NET 4.6.2 though.
At this time, .NET 4,8, .NET Core 3.1 and .NET 6 are currently supported LTS releases. We want to run the unit tests, integration tests and benchmarks only against those frameworks.
Running tests & benchmarks on obsolete TFMs is causing a burden for maintenance since they're no longer available with new VS2022 installs and on the build agents. And I am fairly confident that as long as we target .NET Standard 2.0 and run our tests against those three current LTS releases the library will work on for example .NET Core 2.1 too.
FYI: At some point in the the past we specifically ran tests against .NET 4.6.1/4.6.2 too because of the broken .NET Standard support in there. Those versions are now ancient (8 years) and we're not spending any effort on verifying the lib still works on those old TFMs anymore. You can be fairly certain that version 5.0.0 works on .NET 4.6.2 though.