Home > Articles > Programming > Windows Programming

Introduction to COM and .NET

In this sample chapter, Jimmy Nilsson discusses the history of COM up to the state of .NET today. He touches on key technologies, such as .NET Component Services, Visual Basic .NET, C#, and SQL Server 2000.
This sample chapter is excerpted from Designing for .NET Component Services with VB.NET and SQL, by Jimmy Nilsson, Sams Publishing (ISBN 0672322331).
This chapter is from the book

In this chapter, I will briefly discuss the history of COM up to the state of .NET today. In this discussion, I will tell some horror stories from the dark ages of the Component Object Model (COM), Visual Basic 6 (VB6), and COM+, and will look at the advances made in the industry in recent years. I will also touch on key technologies, such as .NET Component Services, Visual Basic .NET, C#, and SQL Server 2000, that I intend to use for my examples and discussions throughout the book. To understand this chapter and the rest of the book, I assume that you are somewhat familiar with Visual Basic .NET, Common Language Runtime (CLR), and so on, and so I won't discuss these topics in detail in this chapter. With that caveat out of the way, let's get started.

The History of COM, MTS/COM+, VB, and SQL Server

Although we all know that programming didn't start with COM, a major shift in the industry occurred when COM became popular in the mid-1990s, so it seems a good place to start our look at the technology's history. From there, we'll move on to MTS/COM+ Component Services, before touching on VB and SQL Server.


Perhaps one of the most important ideas behind COM was to make it a technique for moving away from monolithic applications toward component-based applications. As such, COM is a binary model, not a source-code model. This might make frequent reuse a little easier to accomplish, because you reuse binary components instead of source-code classes with COM. Another important benefit is the user's ability to take advantage of black-box reuse, which means that the reuser only pulls some ropes to make the component behave as wanted without knowing how the code is written for the component. Black-box reuse was not possible to achieve when source code was reused. If you, as a reuser, are able to view the code you are reusing, it might be more acceptable for the vendor to require knowledge of the implementation of the reused code instead of totally hiding all implementation details, which most often makes life easier for the reuser. That means that the reuser must have a firm grasp of the inner workings of the component it wants to reuse before he or she can make it work correctly.

Another idea behind COM was that it needed to be language-independent; in essence, with COM, programmers are able to choose among several different languages. To make this work, certain rules need to be complied with, and the interfaces of the components must be described with Interface Definition Language (IDL), which is then compiled and transformed into type libraries.

The designers of COM were of the opinion that object-orientation was the way to go, and that object-orientation provided a sound base from which to work. One problem COM addressed was versioning, so that a component could be extended while still being compatible with existing consumers. Meanwhile, COM (or rather DCOM for Distributed COM) also focused on creating a method to split applications so that different parts of the workload can be executed on different machines.

MTS/COM+ Component Services

COM was a big leap in the right direction, but Microsoft Transaction Server (MTS) took COM to the next level. MTS added some runtime services for COM components, such as declarative distributed transactions, declarative role-based security, administrative support, and resource pooling, to name a few. In a way, MTS added services to the operating system that developers who wrote distributed applications previously had to build on their own. Soon after MTS was released, pure DCOM applications became a rarity in the industry.

A friend of mine who works as a project manager often asks me how long it will take me to write a certain program. I always tell him that it will take two days. (That is the universal answer, right?) His response is always one of shock: "How can it possibly take two days to check a check box?" he asks. In fact, with MTS's attribute-based programming, my friend's shock is a bit more justified, because more programming can be accomplished through simple declaration or by setting an attribute value. Transactions in COM+ is one example, referential integrity in SQL Server another.

With Windows 2000, MTS was upgraded to COM+. While MTS was actually an add-on to Windows NT, COM+ was natively supported by Windows 2000. This simplified the programming model quite a bit. It was often said that MTS + COM = COM+. In essence, COM+ joined these two previously separated parts. In addition, COM+ added component services, such as Object Pooling (OP), Compensating Resource Manager (CRM), and Queued Components (QC).


I started my adventures in Windows programming with VB1. I still remember my first major mistake in that environment. It's actually rather embarrassing to share, but it makes me sentimental in a nice way. I was supposed to build a menu application from which several other applications should be started. It was an early "portal" of sorts. My boss wanted me to use pictures instead of text on the buttons, so I used picture boxes instead of command buttons. Unfortunately, I managed to insert pictures, each having a size of approximately 200KB, but only 1KB was actually of interest and shown from each of them. The exe was over 2MB large, which made for very slow startup on the hardware at that time, especially in relationship to what a rocket-science application it was.

Several years and many mistakes later, VB4 was released. It was the first really COM-competent version of Visual Basic. Still, it wasn't until VB5 and VB6 that the COM programming in VB became popular. One of the great (but sometimes also negative) aspects of VB is that it hides several details of COM, such as class factories, reference counting, user-defined interfaces (if desired), IDL, and QueryInterface. You can't achieve as good a performance out of VB as you can from C++, but the productivity is very good. Still, in some camps, VB is considered more of a toy than a tool for a professional programmer. In fact, I've been asked more than once if I get paid to program in VB. The good news is that Visual Basic .NET will change the opinions of some of those who see VB as just a toy. So you no longer have to be embarrassed to admit it if it is your favorite programming language.

SQL Server

I learned SQL at the university in the late 1980s, and it is still useful today. Actually, it's more important to master than ever, especially if you find scalability vital for your applications. Since I started working with SQL Server (version 4), its programming model, with its triggers and stored procedures, has remained quite consistent. For example, the shift from version 6.5 to version 7 was a major one at the engine level, but T-SQL didn't change that much at all.

A friend of mine once said, "Database design is important. Databases are used in 102% of all applications today." I think many developers agree that databases are used a lot. I also think that there is a large difference in opinion regarding whether the database tier—such as SQL Server 2000, for example—should be used for data-focused logic.

I fall on the extreme yes side. You will see me present my position throughout the book; stored procedures, for example, will have a central role in several of the proposed solutions. However, even though I am fond of using database capabilities, I definitely want to encapsulate the access calls to them so they are not visible to more layers than necessary.

Now, let's turn our attention to .NET, which can be seen as the fourth version of COM (after pure COM, MTS, and COM+). Saying that, COM is dead, but long live COM (now called .NET)!

A Few Important Definitions

Before we get too far along in the book, I'd like to define a few terms I will be using in these chapters that have many different meanings in the industry:

  • Component—If you agree with Szyperski5, the word "component" refers to a COM server, such as a DLL or a .NET assembly, that is a binary collection of classes. The COM+ definition of the word refers to one single binary class. I prefer this COM+ definition.

  • Tier and layer—I used to think the terms tier and layer were synonyms. Over the last few years, I have come to understand that layer is logical, while tier is physical. Unfortunately, this explanation isn't very distinct. For example, I like to think of the server-side components as one tier and SQL Server as another, but sometimes they execute physically at the same machine. Therefore, in this book, I will use the word tier to refer to the execution environment and layer to refer to a logical slice of a tier. Typical execution environments include ASP.NET, SQL Server, COM+, Web browser, XML Web Services, and Ordinary Win32 exes.

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.


Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.


If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.


This site is not directed to children under the age of 13.


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020