Rating: 
Summary: A must-have for anyone serious about .NET
Review: This is an amazing reference book for COM and P/Invoke interop (i.e. Win32 interop), an essential topic that most .NET books don't cover well enough. It's essential if you're migrating to .NET, or even if you're writing a non-trivial .NET application from scratch since the .NET Framework has many holes in functionality that must be filled by using interop.I was skeptical because I've had bad luck with Sams books in the past, but this book is wonderful! It's incredibly thorough, complete, and has lots of useful examples and great sidebars. The author's expertise really shines through... It covers things I couldn't find anywhere else (and I've looked at other Interop books) such as an in-depth treatment of custom marshaling, and I really enjoyed the last chapter with Windows Media Player that demonstrated how to expose existing COM APIs as brand new .NET-looking APIs with very little code. The chapters are self-contained, clearly organized, and jam-packed with information. I swear, each page I learned something new, and that's a lot of pages! It answered all of my questions and doubts about .NET interop. I can't imagine doing .NET programming without this book.
Rating:
Summary: There is no other book covering a topic so well
Review: Moving to .NET doesn't mean throwing away your COM code. Integrating the 2 worlds (managed and unmanaged) is achieved via COM Interoperability and there are 2 main scenarios:
1. Writing .NET clients that use COM servers
2. Writing .NET servers to be used by COM clients This 1500 pager is split into 9 parts containing 24 chapters and 6 appendices. In my opinion, the heart of this work lies in parts 2-5 (650 pages, 14 chapters) that thoroughly detail how to write perfect .NET components for COM clients, COM components for .NET clients, .NET clients for COM components and COM clients for .NET components. Trust me (and anyone that has read this book), there is absolutely nothing else left to be said about the topic. The remaining 3 parts cover PInvoke (talking to Win32 dlls), advanced topics such as custom marshaling and two comprehensive examples. The quality throughout is of the highest level. It is a joy to read and full of technical information, a lot of it not found anywhere else. Own this book and forget the online help or any internet sites when it comes to interoperability. The examples used throughout the book are not overly complex or academic or basic; they are just right. Such a balance is hard to strike. What is also hard to find is a book that treats both VB & C++ developers equally. Many authors will benefit by reading Nathan's writings to learn how to achieve that. Whether you plan to write C# or VB.NET code and whether your COM components were written in C++ or VB6 you will not feel left out or bored going through the chapters. Although large, it can be read linearly and it will definitely serve as a reference text on your shelf. I particularly enjoyed the sidebars (categorised as FAQ, Digging Deeper, Tip, and Caution) which are full of golden information. I could go on praising it but suffice to say that it could easily be sold with money-back guarantee and not a single book would be returned.
Rating: 
Summary: This book is not for c++ developers
Review: If you want to write in c# this book is for you. The author is very verbose.
Rating:
Summary: Very detailed treatment of .NET/COM interop
Review: This book represents a very detailed analysis of the issues that arise from interoperating between .NET and COM. The book describes the issues involved in using COM components within .NET with the same attention to detail as those in designing .NET components that are used within "legacy" COM apps. The book closes with a detailed discussion of P/Invoke and some more advanced topics such as custom marshalling. The sheer size of the book might be frightening to some but the book's structure makes it easy to pick up exactly what you need. For example, each major part starts off with an example-rich introductory chapter that is a great help in getting started with interop. On the other hand, the book allows the reader to really dig into the minute details of interop. I particularly liked that the book provides lots of valuable design guidelines and an abundance of realistic code examples. Maybe not a book that one wants to read front to cover but an invaluable reference and troubleshooter for anyone who works in the interop area and needs to understand what is really going on under the covers. The most complete work on this important topic yet.
Rating:
Summary: Well Worth the Money
Review: Currently, this is *the* reference book for the subject area of .NET interop with COM and other unmanaged code via P/Invoke. At almost 1600 pages, it can seem daunting but just treat it like a reference. Open up to the chapter that covers what you are interested in, such as "The Essentials of using COM in Managed Code" (chapter 3) or "The Essential of PInvoke" (chapter 18) or "Customizing COM's View of .NET components" (chapter 12). This last one is one of my favorites because it shows how you have more flexibility in writing COM components in .NET than you have with VB 6. Another thing I really like about this book is that it has lots of sidebars with tons of useful information that I haven't found anywhere (at least not easily) in the current .NET docs. Heck, even the appendix is chock full of good stuff like mappings between COM HResults and .NET exceptions and PInvoke definitions for the Win32 API.
Rating:
Summary: Truly is the Complete Guide
Review: 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.
Rating: 
Summary: Comprehensive interoperability book
Review: 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++.
Rating:
Summary: The cards were stacked against it. It came out good.
Review: 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.
Rating:
Summary: This book is not for c++ developers
Review: If you want to write in c# this book is for you. The author is very verbose.
Rating:
Summary: Great .Net Inteop Guide
Review: This is a great book that covers .Net Interop. It covers Interop more in debth compared to other books that I have read. All the ideas covered apply to Visual Studio 2002 and as well as Visual Studio 2003. The book is well layed out and information is easy to find.
| 
