CoreFx still builds packages that have desktop reference assemblies

[ericstj]

Related https://github.com/dotnet/corefx/issues/23830, part 3

We still have some packages that have reference assemblies in their ref folder. We've found numerous tools that don't like this and shouldn't expect all those tools to get fixed.

As such, we need to tactically remove ref folders, or use the implementation instead in these cases.

[ViktorHofer]

@joperezr any idea how many packages are affected here?

[joperezr]

I don't know from the top of my head, but it should be easy to find out how many are there, since all we need to do is to do a build.cmd -allConfigurations and then search in the package nuspecs to find all places where we have "ref/net4" as target path. That said, in order to fully fix this it won't be enough to just remove those, we will also have to find if there any other packages where we have a reference asset for a different framework (like netstandard2.0) which will be used when targeting desktop.

[ViktorHofer]

cc @Anipik as you are looking into reducing the number of reference assemblies in package while migrating pkgprojs to csprojs.

[ViktorHofer]

Closing as we don't include reference assemblies in packages anymore.