Visual Studio 2010: Embed Interop Types

visual-studio-2010 clr com-interop pia
ollifant picture ollifant · Oct 20, 2009 · Viewed 11.1k times · Source

I found some information about this on Scott Hanselmans Blog

Does anybody exactly know what this mean?

Is this only for the Office Primary Interop Assemblies, or can I also use this to Embed my Redemption library or other COM libraries?

Answer

Robert Harvey picture Robert Harvey · Oct 20, 2009

The process described in Scott Hanselman's blog is called Type Equivalence, a rather nebulous term for the CLR 4.0's support for COM interop type assemblies. Although I haven't had a chance to look at it, there is a video here at Channel 9 that discusses it:

Raja Krishnaswamy and Vance Morrison: CLR 4 - Inside Type Equivalence
http://channel9.msdn.com/shows/Going+Deep/Raja-Krishnaswamy-and-Vance-Morrison-CLR-4-Inside-Type-Equivalence/

Apparently you can write your own "type equivalence" assemblies, and embed them. Note that this probably does not apply to just any COM assembly; type equivalence assemblies implement an interface called IApplication. See here:

Advances in .NET Type system: Type Equivalence Demo http://blogs.msdn.com/mshneer/archive/2008/10/28/advances-in-net-type-system-type-equivalence-demo.aspx

Related questions

the common language runtime was unable to set the breakpoint

This is actually another part of this question. Error settings breakpoints but only on some lines while debugging I'm remote debugging a CRM 2011 plugin in vs 2010. I'n one of my source files I can set breakpoint all throughout the code …

Read More
CLR/CLI linker fails with error LNK2022 - Custom attributes are not consistent

Environment: Visual Studio 10, CLR/CLI Class Library project, built with Platform Toolset v100, targeting framework version v3.5. I am aware that this question was already asked here, but I did not find an answer that solved the problem for my …

Read More
The type or namespace name could not be found

I have a C# solution with several projects in Visual Studio 2010. One is a test project (I'll call it "PrjTest"), the other is a Windows Forms Application project (I'll call it "PrjForm"). There is also a third project referenced by …

Read More