Consume NuGet /embed assets group for interop type assemblies from NuGet package

This is the tracking issue to update dotnet build tasks to consume new /embed assets group from NuGet packages for interop type assemblies so that Project System passes it as link instead of ref to compiler.

Corresponding NuGet issue# https://github.com/NuGet/Home/issues/2365

@livarcocc @nguerrera @dsplaisted @rrelyea

[nkolev92]

You need to build it with ImportedFromTypeLib specified. Here’s what we have in one of our projects: https://github.com/NuGet/NuGet.Client/blob/release-5.11.x/src/NuGet.Clients/NuGet.VisualStudio/AssemblyInfo.cs

[nkolev92]

Should packages using this feature put a DLL in both the lib and embed folders? The spec seemed to suggest this, but since the result of the embed folder is that EmbedInteropTypes metadata should be set to true on the compile reference, it seems like maybe the DLL should only go in the embed folder

It seems like the idea with duplicating was for the package to remain compatible with packages.config.

I think with interop the expectation would be that the assembly gets embed into the final assembly and that’s it. It should not be deployed in the runtime folder.

If it’s in both, we will probably need logic in the ResolvePackageAssets task to deduplicate the items, or to match up the embed items with the lib ones.

I feel like this should’ve been dedupped on NuGet side, but it’s ok if it’s done on the RPA side too.