This product requires some knowledge and experience in coding with .NET and in Visual Studio but it contains all you need to know about the interoperability of .NET and COM. Many hints, detailed information and examples are included and guide through the interoperability of managed and unmanaged components.

My co-worker had a previous edition of this book (now set) and it was the bible for any question regarding .Net/COM interop. When he left the company and took the book with him I was sad. Now it's back in print, however, and happy days are here again.

I'm not going to pretend that I'm a COM God; I'm mostly a desktop .Net component developer who has to expose the component to both managed and unmanaged (COM) clients. This book was invaluable for walking us through some of the trickier steps of integrating our new component with the main client (QuickBooks accounting software) in a way that supported new version deployment and backwards compatibility.

The way that Nathan describes best practices for exposing managed libraries to COM is clear and concise (as much as you can be when talking about COM, I suppose). It directly led to several utilities and build steps we added in order to create better components.

I highly recommend this book set.

I read Troelsen's book on COM/.NET interroperability. This two volume set easily exceeds in content. Both books provide valuable information that I use regularly in developing .NET solutions that use COM as clients and servers. If I had to have only one selection, I would choose these books (Adam Nathan's) for the extensive content.

Never one to skimp on books, I ordered three with almost exactly the same title on COM/.NET Interop when I needed some information on the subject. Adam Nathan's book is by far my favorite. I've never found an answer in another book that wasn't in Nathan's (and have found many in his that I didn't find anywhere else).

It seems like this book isn't as easy to get on amazon as it once was--a pity, because it's the first (and maybe only) Interop book you'll need. Maybe he'll come out with another edition as .NET changes...

This book has been an invaluble resource on a .NET/COM interop project I've been working on. Don Box's quote on the cover sums up the title nicely, "This is the last book that should be written about COM programming. There is nothing left to say."

Since I'm a published author myself, I first bought a book on this topic from my publisher Microsoft Press. While accurate, it left a lot to desire. Very little advanced information was provided. However, this title from Adam Nathan's and Sams Publishing leaves nothing out, including extensive references.

If you are working with COM objects from .NET, or vice-versa, this book will be an excellent resource.

Often finding an appropriate and effective bridge to .NET is a time consuming and problematic task, we had to do a lot of research and benchmarking to find an optimal solution. Having this book by Adam Nathan will save time and effort on building these bridges.

The material in the book is intended for use by experienced professional developers, it's certainly not an entry level tutorial, but the author's style, detailed description supported by examples makes it easy to read and follow. A short introduction to .NET and managed code concepts is provided in the first section of the book. I discovered, however, that this book may be helpful to the people who have no previous COM knowledge, due to the very descriptive and illustrative style.

The author clearly has an extensive experience of COM and a good knowledge of Microsoft .NET. That's why the material is not just an abstract presentation, but a systematically organized guide, focused on potential problems and difficulties a developer may face. However, it is still only focused on COM/.NET interoperability, most probably I would need another book about Java, CORBA working with .NET. The book, as already mentioned, is not an introductory or general conceptual tutorial on programming or architecture, but a very detailed and comprehensive interoperability reference, and it is definitely worth its price. Also the length of the book, about 1600 pages is well justified. Another positive side of the book is that examples are written in VB, C# and managed C++.

The book is 1608 pages - 50% more than a James Michner book. It's published by Sam's. What more could it have against it?

Yet it's a good book. If you're talking between .Net and COM it's got the information you need. Any chapter you open it to has good, readable information when you feel like browsing. It lies flat on a table when opened. What more could you ask for in a book?

Definitely worth the price.