ASP.NETCore contains System.Security.Cryptography.Pkcs but does not expose for reference

[ericstj]

See https://github.com/dotnet/sdk/pull/51343/files/18e7355363b7ecb77ad81f9ff515cb7d6113de7e#r2446270194

PKCS is a dependency of Cryptography.Xml, which is exposed.

We'd like to prune Cryptography.Xml, but doing so will also prune PKCS.

Packages which are part of the shared framework should include and expose their entire closure.

[MihuBot]

I'm a bot. Here are possible related and/or duplicate issues (I may be wrong):

• Upgrading from 5.0 to 6.0 yields InvalidOperationException: Cannot find compilation library location for package 'System.Security.Cryptography.Pkcs #38892
• runtime cannot find System.Security.Cryptography.Pkcs  #38227

[halter73]

PCKS is part of ASP.NETCore and WindowsDesktop. I see the package present in the framework information for WindowsDekstop, but absent from ASP.NETCore. It looks to me like ASP.NETCore might not even expose this reference. I see the assembly is in the shared framework but not the ref-pack.

https://github.com/dotnet/sdk/pull/51343/files/18e7355363b7ecb77ad81f9ff515cb7d6113de7e#r2446270194

@wtgodbe Do you know what we need to do to fix the ASP.NET Core ref-pack here?

[wtgodbe]

This has been the case for a while, reference resolution used to put it in the SharedFx but not the Targeting Pack (it was a transitive ref of something we used in the SharedFx). We've since added extra logic to maintain that behavior, which was probably unnecessary. Testing that w/ #64172