ComInterop

[me]

What is the downside of Cominterop? is it good practice? what does it do to
memory?

Thanks

[Mattias Sjögren]

>What is the downside of Cominterop?

Calling into native code requires a high level of trust, and has a
certain overhead compared to calls between managed components.

is it good practice?
Well often you don't have a choice, you use it when you have to.

what does it do to memory?

Not sure exactly what you mean here. I don't think COM interop affects
memory use in any significant way. But marshaling of parameter data
may of course require some extra memory.

Mattias

--
Mattias Sjögren [MVP] mattias @ mvps.org
http://www.msjogren.net/dotnet/ | http://www.dotnetinterop.com
Please reply only to the newsgroup.

[Bennie Haelen]

I would say that some of the main downsides of COM Interop is the
overhead of marshalling your parameters to the COM component. In
general, you should use COM interop when you need to interact with an
existing COM component. It is always preferable to have a "pure" .NET
solution, but is some cases, it might be budget- or time prohibitive to
rewrite existing components.

- Bennie
me wrote:

What is the downside of Cominterop? is it good practice? what does it do to
memory?

Thanks