Is COM still relevant

[Raj]

I want to develop a C++ class library. I finally realised I need COM not just
C++ Dll. Is developing COM as dll useful or should I consider any .Net
related technology. Is COM relevant or when to chose COM than .Net and when
to use related .Net technology.

Thanks,
Rajesh

[Joshua Flanagan]

Choose COM if you need the class library to be available on a wide
variety of systems, where you cannot guarantee the .NET Framework will
be available.
If you have control of over where the library will be deployed, or can
at least guarantee that the .NET Framework will be available, I see no
reason not to use .NET. You will get the benefits of managed code, and
can still be used by COM clients (as long as you design the classes to
be COM compatible).
Raj wrote:

I want to develop a C++ class library. I finally realised I need COM not just
C++ Dll. Is developing COM as dll useful or should I consider any .Net
related technology. Is COM relevant or when to chose COM than .Net and when
to use related .Net technology.

Thanks,
Rajesh

[Raj]

I will be using it on Windows 2000/XP/Embedded XP. I would use it with VB
6.0, VC++ 6.0 applications and with .Net apps in future if required.

"Joshua Flanagan" wrote:

Choose COM if you need the class library to be available on a wide
variety of systems, where you cannot guarantee the .NET Framework will
be available.
If you have control of over where the library will be deployed, or can
at least guarantee that the .NET Framework will be available, I see no
reason not to use .NET. You will get the benefits of managed code, and
can still be used by COM clients (as long as you design the classes to
be COM compatible).
Raj wrote:

I want to develop a C++ class library. I finally realised I need COM not just
C++ Dll. Is developing COM as dll useful or should I consider any .Net
related technology. Is COM relevant or when to chose COM than .Net and when
to use related .Net technology.

Thanks,
Rajesh