doubt on COM components

[kn_kirankumar]

I heard that we should try to avoid COM components as
possible as much while developing an application in .NET,
Why we need to avoid COM components?
Is there any serious reason?

[Herfried K. Wagner [MVP]]

* "kn***********@yahoo.com" <an*******@discussions.microsoft.com> scripsit:

I heard that we should try to avoid COM components as
possible as much while developing an application in .NET,
Why we need to avoid COM components?
Is there any serious reason?

Using COM components causes a lot of marshalling overhead which may
reduce performance and consume memory.

--
Herfried K. Wagner [MVP]
<URL:http://dotnet.mvps.org/>
<URL:http://dotnet.mvps.org/dotnet/faqs/>

[Samuel L Matzen]

You should use .NET components if they are available. But for a robust
application you many need to use some COM components. They will work just
fine, but the interface between .NET and COM inserts some overhead, so if
you are hitting the COM components thousands of times a second you will
probably see some performance degradation.

-Sam Matzen
"kn***********@yahoo.com" <an*******@discussions.microsoft.com> wrote in
message news:34****************************@phx.gbl...

I heard that we should try to avoid COM components as
possible as much while developing an application in .NET,
Why we need to avoid COM components?
Is there any serious reason?

[Chris Dunaway]

On Sat, 24 Jul 2004 02:51:21 -0700, kn***********@yahoo.com wrote:

I heard that we should try to avoid COM components as

In addition to the other comments, one final reason for not using COM
coponents is that it complicates deployment. You no longer have XCopy
deployment and have to register the COM components on the target machine.
Thus, the possibility of "dll hell" still exists.

Like any tool, use them where necessary.

--
Chris

dunawayc[AT]sbcglobal_lunchmeat_[DOT]net

To send me an E-mail, remove the "[", "]", underscores ,lunchmeat, and
replace certain words in my E-Mail address.