Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>There is a good book called <a href="http://rads.stackoverflow.com/amzn/click/067232170X" rel="noreferrer">.NET and COM: The Complete Interoperability Guide</a> that I am about to start reading as I want a better understanding of COM interop. Maybe it would be useful for you too, check it out.</p> <blockquote> <p>The focus of the book is on COM Interoperability (since it's a much larger subject), and the heart of the discussion is broken down into four parts:</p> <pre><code>* Using COM Components Within the .NET Framework * Using .NET Framework Components from COM * Designing Good .NET Framework Components for COM Clients * Designing Good COM Components for .NET Framework Clients </code></pre> <p>The scope of the book is just about everything related to using "unmanaged code" in the .NET Framework. Technologies built on top of COM Interoperability are also covered-Interoperability of Windows Forms Controls and ActiveX controls, Interoperability with COM+, and Interoperability with Distributed COM (DCOM). Although Platform Invocation Services is a separate technology from COM Interoperability, there are many areas of overlap, so including in the book is a natural fit. All of these technologies are a core part of the Common Language Runtime and .NET Framework, and will likely be used not only as the path of migration for existing software projects, but for brand new software development for the next several years</p> </blockquote> <p>Also have a look at this (legally) free pdf ebook <a href="http://www.theserverside.net/tt/articles/showarticle.tss?id=ComAndDotNetInterop_Book" rel="noreferrer">COM and .NET Interoperability</a> which you can download from TheServerSide.com. You have to register before you can download, but you can just <a href="http://www.bugmenot.com/view/theserverside.com" rel="noreferrer">bugmenot</a> if you don't feel like it.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload