In Effective COM, the authors, Don Box, Keith Brown, Tim Ewald, and Chris Sells, offer 50 concrete guidelines for creating COM based applications that are more efficient, robust, and maintainable. Drawn from the authors extensive practical experience working with and teaching COM, these rules of thumb, pitfalls to avoid, and experience-based pointers will enable you to become a more productive and successful COM programmer. These guidelines appear under six major headings: the transition from C++ to COM; interfaces, the fundamental element of COM development; implementation issues; the unique concept of apartments; security; and transactions. Throughout this book, the issues unique to the MTS programming model are addressed in detail. Developers will benefit from such insight and wisdom as: *Define your interfaces before you define your classes (and do it in IDL) *Design with distribution in mind *Dual interfaces are a hack. Dont require people to implement them *Dont access raw interface pointers across apartment boundaries *Avoid creating threads from an in-process server *Smart Interface Pointers add at least as much complexity as they remove *CoInitializeSecurity is your friend