Use ridless PNSE configurations where applicable (#44230)
authorViktor Hofer <viktor.hofer@microsoft.com>
Thu, 10 Dec 2020 20:05:34 +0000 (21:05 +0100)
committerGitHub <noreply@github.com>
Thu, 10 Dec 2020 20:05:34 +0000 (21:05 +0100)
commita03ab4393908c7cc910a7b68f44fdbfca48f8a68
treebc301cbed9ce1c30442b6c1eab64765e445a9c34
parentdf6ff0fbfa2c107ed710db12fcbf434fc933ea2c
Use ridless PNSE configurations where applicable (#44230)

For projects that require platform support we should use a rid-less
configuration, i.e. $(NetCoreAppCurrent). That guarantees that PNSE
assemblies are available for new configurations that aren't represented
in the defined project's TargetFrameworks. This is especially important
for inbox assemblies.

I left the following assemblies as is as they are partial PNSEs:
- System.Security.Cryptography.Algorithms
- System.Net.NameResolution

System.Net.Requests and System.Net.WebClient are IL only but
intentionally marked as throwing on Browser.
src/libraries/System.Net.HttpListener/src/System.Net.HttpListener.csproj
src/libraries/System.Net.NetworkInformation/src/System.Net.NetworkInformation.csproj
src/libraries/System.Net.Ping/src/System.Net.Ping.csproj
src/libraries/System.Net.Security/src/System.Net.Security.csproj
src/libraries/System.Net.Sockets/src/System.Net.Sockets.csproj