Why Build a .NET Component to Look Like a COM Component?
The previous two chapters showed why .NET should and does interoperate with existing COM components and DLLs. The reasons why existing COM components and DLLs should be able to interoperate with .NET are similar yet different. You want to have access to existing COM components and DLLs so that any development does not need to involve a full port of the functionality that has already been developed. Interop in the other direction (from legacy code to .NET) allows development to be done with the tools and facilities of the .NET Framework and still have the code accessible from legacy code (unmanaged code). In addition, consider the following as you consider your next project:
Many significant ...
Get .NET Common Language Runtime Unleashed now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
