What are the practical limitations of using COM objects?

Q

Managed Code and Unmanaged Code related ASP.NET - What are the practical limitations of using COM objects?

✍: Guest

A

The following are the practical limitations of using COM objects from .NET:

Shared solutions might not allow COM objects : ASP.NET host service providers that use nondedicated servers can limit or prohibit the installation of COM objects on their servers. COM objects are prone to memory leaks : COM uses reference counting to determine when to destroy objects and free memory. It is possible for this reference count to become incorrect, leaving objects in memory indefinitely.

Type libraries might be inaccurate : Because COM separates the object’s description from its implementation, it’s possible for this description to not accurately reflect the object. In this case, the generated interop assembly will also include those inaccuracies.

COM is unmanaged code : All the limitations of unmanaged code apply to COM objects as well.

2009-04-21, 5084👍, 0💬