Review NetCoreAppCurrent libraries configurations which are platform specific

[ViktorHofer]

System.Data.Odbc has a big number of platform specific configurations. As those are now shipping as part of https://github.com/dotnet/runtime/pull/53439, it might make sense to review and see if some of these configurations could be collapsed together.

System.Text.Encodings.Web targets a Browser even though it doesn't use any platform specific APIs. Apparently this is so that the linker can trim out Vector128 on browser-wasm: https://github.com/dotnet/runtime/pull/53439#discussion_r643263009. We should see if there's a better way to make this work without the platform specific configuration.

EDIT: In addition to that, we need to make sure that all dependencies from the platform TFMs are represented in the platform agnostic TFM.

cc @ericstj @eerhardt @MichalStrehovsky @marek-safar @ajcvickers

[ghost]

Tagging subscribers to this area: @Anipik, @safern, @ViktorHofer See info in area-owners.md if you want to be subscribed.

Issue Details

---

System.Data.Odbc has a big number of platform specific configurations. As those are now shipping as part of https://github.com/dotnet/runtime/pull/53439, it might make sense to review and see if some of these configurations could be collapsed together. System.Text.Encodings.Web targets a Browser even though it doesn't use any platform specific APIs. Apparently this is so that the linker can trim out Vector128 on browser-wasm: https://github.com/dotnet/runtime/pull/53439#discussion_r643263009. We should see if there's a better way to make this work without the platform specific configuration. There are probably more of these cases and I will add a list of packages to review at a later point. cc @ericstj @eerhardt @MichalStrehovsky @marek-safar @ajcvickers

Author:	ViktorHofer
Assignees:	-
Labels:	`area-Infrastructure-libraries`
Milestone:	6.0.0

[eerhardt]

cc @GrabYourPitchforks for the System.Text.Encodings.Web part as well.

[ViktorHofer]

Here's a list of projects that are packable and multi-target based on the TargetFramework and TargetPlatform, ordered by the number of assemblies in the correspnding package when we ship .NET 8:

• System.Data.Odbc.csproj (25)
• System.DirectoryServices.Protocols.csproj (13)
• System.IO.Ports.csproj (11)
• System.Security.Cryptography.Pkcs.csproj (9)
• Microsoft.Win32.Registry.AccessControl.csproj (8)
• Microsoft.Win32.SystemEvents.csproj (8)
• System.Data.OeDb.csproj (8)
• System.Diagnostics.EventLog.csproj (8)
• System.Diagnostics.PerformanceCounter.csproj (8)
• System.Net.Http.WinHttpHandler.csproj (8)
• System.Text.Encoding.CodePages.csproj (8)
• System.Text.Encodings.Web.csproj (8)
• System.Threading.AccessControl.csproj (8)
• System.Security.Cryptography.ProtectedData.csproj (8)
• System.ServiceProcess.ServiceController.csproj (8)
• System.DirectoryServices.csproj (7)
• System.DirectoryServices.AccountManagement.csproj (7)
• System.Management.csproj (7)
• System.Runtime.Caching.csproj (7)
• System.Speech.csproj (7)
• System.Windows.Extensions.csproj (6)

[eerhardt]

One library in the list that surprises me is System.Runtime.Caching. It doesn't seem like it should need to be target platform-specific.