Migration versus Interop

For the purposes of this chapter, migration is the process of taking unmanaged code that was written using the various technologies in Windows DNA, such as COM, MTS, COM+, ADO, ASP, or Win32, and converting that code to use managed code and the technologies in the .NET Framework, such as XML Web services, .NET remoting, serviced components, ADO.NET, and ASP.NET. Interop means using the various Interop technologies provided by the .NET Framework (primarily COM Interop and P/Invoke) to call existing COM or COM+ components and unmanaged APIs. Using migration and Interop are not mutually exclusive; in fact, they complement each other. Most software development organizations cannot afford to migrate their entire application ...

Get .NET and COM Interoperability Handbook, The 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.