How This Book Is Organized
The term COM+ is a marketing term and, as such, tends to confuse certain things. For example, people sometimes get confused about the distinction between the abbreviations COM, DCOM, MTS, and COM+. In reality, the term COM+ refers to two things. First, COM+ represents the integration of the COM model with the MTS services model. Second, COM+ refers to a series of services that Microsoft provides for you, like distributed transactioning, role-based security, easy deployment of your application, and so forth. The acronym COM in many ways sounds old in comparison to COM+, but this is just a side effect of the marketing effort. In reality, COM and COM+ are the same thing when it comes to how the components are made. COM+ components are COM components, and COM components are now called COM+ components.
With that in mind, the book is organized as follows:
- Chapter 1
Explains the progression from COM to DCOM to MTS, COM+, and finally .NET. It is meant to provide you with an overview of what Microsoft has been trying to accomplish with component technology for the last eight years and where we are headed later this year and next year.
- Chapter 2
Explains the benefits of using interfaces in your programming and shows how interfaces are crucial for versioning. It also explains why COM uses interfaces.
- Chapter 3
Explains what interfaces look like at the memory level. The chapter is meant to expose you to how the VB compiler generates VB COM objects in memory. It also ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access