Summary

I l @ ve RuBoard

Many COM issues that you are likely to encounter were touched on in this chapter. Issues such as consuming COM within a Managed Client, exposing Managed code as classic COM, COM threading models, and the notion that COM supports only a subset of what can be accomplished with C# and the CLR. It is likely that classic COM will exist for years to come, thus requiring most developers to learn the basics of COM Interop with Managed code. For future projects, I would suggest moving away from the restrictions of classic COM. Focus instead on maximizing your return with the facilities provided by C# and language interop for component-based applications.

C# affords a very powerful language for component construction, and .NET facilitates language interoperability that is unparalleled. To effectively interoperate outside of .NET still requires knowledge of the target client and its support for interop . With the large amount of classic COM in existence, chances are that most of your projects will require the consumption of those COM object by a Managed client. Luckily, you've got .NET on your side.

I l @ ve RuBoard