InfoQ

News

Is COM a Dying Technology?

Posted by Jonathan Allen on Aug 21, 2007 06:27 AM

Community
.NET
Topics
Change
Tags
migration,
Coding Standards

Component Object Model or COM was invented by Microsoft in 1993. It included a number of features that allowed applications to communicate with one another in a language agnostic fashion. A number of technologies fall under the Com umbrella including OLE, ActiveX, DCOM, and COM+.

Many of the features found in COM have since been replaced by .NET and the CLR. With languages sharing a common runtime, COM's method for exposing object libraries is no longer needed. .NET remoting replaces DCOM, and unlike ActiveX controls, downloadable libraries written in .NET can be verified for safety.

This is all theory. In reality, the picture is much more complex. The COM based language, Visual Basic, is still a major platform for many companies even though it is no longer supported in any meaningful fashion. And COM is still the technology of choice for Microsoft Office as wells as countless other applications. Even Windows Vista exposes some new functionality via COM libraries.

So the question remains, is COM a dying technology or something that will be seen for many years to come?

8 comments

Reply

If you have to ask... by Weiqi Gao Posted Aug 21, 2007 7:34 AM
COM live to its replaced in Microsoft office by robert shell Posted Aug 21, 2007 8:00 AM
Re: COM live to its replaced in Microsoft office by Diego Vega Posted Aug 21, 2007 11:15 AM
Re: COM live to its replaced in Microsoft office by Jonathan Allen Posted Aug 22, 2007 12:12 AM
is COM a dying technology or something that will be seen for many years...? by Stefan Wenig Posted Aug 21, 2007 9:02 AM
Did I miss something? by Kevin Williams Posted Aug 21, 2007 9:58 AM
Not close to being "dead" by Peter Ritchie Posted Aug 22, 2007 4:07 PM
COM is dead to me by Harry Chou Posted Aug 22, 2007 8:13 PM
  1. Back to top

    If you have to ask...

    Aug 21, 2007 7:34 AM by Weiqi Gao

    ... it's not dead.

  2. Back to top

    COM live to its replaced in Microsoft office

    Aug 21, 2007 8:00 AM by robert shell

    As long as MS-Office integration is important then COM will lives on. Afraid once you attempt to add functionality too Excel or add in-place data displays in Word your back to COM land. As of Office 2003 there are wrapper now work (mostly) but COM still the key. In fact COM still appears to be the high water mark for runtime application integration. What really replaces OLE and in place activity in dot net. In the .Net environment appear much focused on development time library/component integration and no application integration.

  3. Both, of course. This is so obvious I wonder why anyone would bother to ask that question.

  4. Back to top

    Did I miss something?

    Aug 21, 2007 9:58 AM by Kevin Williams

    That would imply that COM is still alive, wouldn't it? That's news to me, I thought COM died the day .NET came out. :)

  5. Agreed about Office being one of the main reasons COM is still alive. Also an interesting observation about .NET lacking some application integration features, but I think it improves a lot with WCF. What I think we won't ever see is a .NET based document format and embedding mechanism, but that is because we now have and prefer XML. What amuses me sometimes is that all those cool new browser extensions we see comming from Windows Live and Microsoft Research seem to be ActiveX controls for IE and Firefox plug-ins. It seems that COM is still the way to go if you want to do something to extend IE in C++. I wonder how much of this will change in the comming years.

  6. Back to top

    Re: COM live to its replaced in Microsoft office

    Aug 22, 2007 12:12 AM by Jonathan Allen

    What I think we won't ever see is a .NET based document format and embedding mechanism, but that is because we now have and prefer XML.
    I'm not so certain about that. Even if XML is the format of choice, you still need something to render it.

  7. Back to top

    Not close to being "dead"

    Aug 22, 2007 4:07 PM by Peter Ritchie

    Although direct use by end-users is on the decrease, technologies like .NET are using COM in the background. .NET was once named COM3. COM is still the main technology to extend dozens and dozens of aspects of Windows and Internet Explorer. It's not going anywhere anytime soon.

  8. Back to top

    COM is dead to me

    Aug 22, 2007 8:13 PM by Harry Chou

    If I have a choice, I won't write anything with COM as the main platform. To me, COM is dead ... I know there are places COM is required. Again, if you have choice, will you write your next app in VB6?

Exclusive Content

Rob Windsor on WCF with REST, JSON and RSS

WCF is not just for SOAP based services and can be used with popular protocols like RSS, REST and JSON. Join Rob Windsor as he introduces WCF 3.5 and its new native support for non-SOAP services.

Christophe Coenraets Discusses Flex 3, AIR, and BlazeDS

Christophe Coenraets discusses Flex 3, Flex Builder, AIR, BlazeDS, Adobe and open source, integrating Flex with existing applications, and integrating RIAs with search engines and browsers.

Debunking Common Refactoring Misconceptions

Danijel Arsenovski attempts to dispel some of the myths around refactoring and how it applies to .NET developers.

REST Eye for the SOA Guy

In this presentation, recorded at QCon San Francisco, CORBA guru Steve Vinoski explains REST from the view of someone who comes to SOA from a traditional, RPC-oriented background.

Choose Feature Teams over Component Teams for Agility

Feature teams are key to scaling agility for large teams. In an excerpt from "Scaling Lean and Agile Development," Larman & Vodde show how feature teams resolve traditional problems & raise new issues

Billy Newport explains Virtualization

Billy Newport talks about virtualization, eXtreme Transaction Processing (XTP) and WebSphere Virtual Enterprise. He discusses hardware, hypervisor, JVM, application and data virtualization.

Virtualization and Security

While virtualization provides many benefits, security can not be a forgotten concept in its application.

Introduction to Agile for Traditional Project Managers

This session is specifically aimed at traditionally trained project managers who are new to Agile, and who would like to be able to relate the PMI's best practices to their Agile equivalents.