Consume NuGet /embed assets group for interop type assemblies from NuGet package
See original GitHub issueThis 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
Issue Analytics
- State:
- Created 5 years ago
- Reactions:1
- Comments:14 (12 by maintainers)
Top Results From Across the Web
Create packages with COM interop assemblies
Create NuGet packages that contain COM interop assemblies ... use a combination of your package name and the assembly being embedded, ...
Read more >Embed Interop Types to false in NuGet package
There's an assembly I need to reference in my project, that needs to have the "Embed Interop Types" set to false in order...
Read more >Microsoft.VisualStudio.SDK.EmbedInteropTypes 15.0.36
When referencing VS SDK NuGet packages using PackageReference, assemblies are referenced instead of linked. This package corrects that.
Read more >Conflict between Asset's Newtonsoft and ...
Hey guys, (Unity 2019.3.4f1) So i want to start my new project and i wanted to use Entities in it. I have already...
Read more >What is NuGet (How it Works for Developers Tutorial)
NuGet enables the production, hosting, and retrieval of packages for .NET Frameworks. Software packages that NuGet manages are called NuGet ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
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
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.
I feel like this should’ve been dedupped on NuGet side, but it’s ok if it’s done on the RPA side too.