When we say we want to migrate the existing C++ code to .NET Framework, the first question that comes to our mind is What is the need to migrate the existing code to .NET Framework when it supports the interoperability with the existing C++ code? The answer lies in the extent of support provided for the interoperability with existing C++ code, the overhead associated with the interoperability, and the ability to exploit the various features provided by it.
We start with the extent of support provided by .NET Framework for interoperability with existing C++ code. There are four aspects to this:
Calling an existing COM component from .NET Framework
Calling a .NET component from unmanaged code
Calling unmanaged ...