NightOwl888 commented on issue #1040: URL: https://github.com/apache/lucenenet/issues/1040#issuecomment-2487619240
Well, dropping them both is something to consider. Most of the issues we have with testing .NET Standard are because as you stated, there are not very many platforms where they are still supported. It certainly would make testing easier if we didn't have to apply `SetTargetFramework` to override the target under test with a platform that is no longer officially supported. Not to mention, if we transition to testing NuGet packages instead of publishing binaries it will mean we don't need to pack extra NuGet packages that only have the target under test in it just so it will be resolved with the right target under test. `PackageReference` doesn't have an equivalent to `SetTargetFramework`, so that is the best we can do. That being said, I am not sure about dropping support for Unity just yet. They [are still working on supporting .NET Core](https://discussions.unity.com/t/unity-future-net-development-status/836646). According to ChatGPT there have only been a few previews released, but so far no RTM release. So, keeping a `netstandard2.1` target until that transition is complete is probably a good idea. As for Mono, I don't think it is such a big concern as it is being phased out in favor of .NET Core in most cases, but keeping `netstandard2.1` would also allow those who are still in the process of transitioning time to finish their migration. >> Requiring higher versions of most other platforms that are still in support > What do you mean by this? As you point out, which is a really good point, .NET Framework isn't going to use our netstandard2.0 build anyways. UWP was deprecated in 2021, and is only expected to receive bug fixes, so I assume you're not referring to that. Xamarin is no longer in support, and the supported versions of .NET (8 and 9) will use our net8.0 build. So the only question mark would be Unity and Mono. Yes, as you astutely pointed out, all that are really left are Unity and Mono. Modern versions of these are both supported on `netstandard2.1`, which makes the supported audience for `netstandard2.0` effectively zero. That is, other than the convenience of having a single target framework for libraries that depend on us (which comes at a significant performance cost) and any stragglers that are still supporting UWP. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
