native-and-dotnet-interoperability.md

title	ms.custom	ms.date	ms.reviewer	ms.suite	ms.technology	ms.tgt_pltfrm	ms.topic	dev_langs	helpviewer_keywords	ms.assetid	caps.latest.revision	author	ms.author	manager
Native and .NET Interoperability | Microsoft Docs		11/04/2016			cpp-windows		article	C++	interop [C++] .NET Framework [C++], interoperability with Visual C++ interoperability [C++], about .NET interoperability interop [C++], about .NET interoperability managed code [C++], interoperability native code [C++] interoperability [C++] MFC [C++], .NET integration unmanaged code interoperability [C++] Visual C++, interoperability native code [C++], .NET interoperatibility	f3ec6c99-c745-4256-b95b-f1d12ba17a5a	16	mikeblome	mblome	ghogen

Native and .NET Interoperability

Visual C++ supports interoperability features that allow managed and unmanaged constructs to co-exist and interoperate within the same assembly, and even in the same file. A small subset of this functionality, such as P/Invoke, is supported by other .NET languages as well, but most of the interoperability support provided by Visual C++ is not available in other languages.

In This Section

Mixed (Native and Managed) Assemblies
Describes assemblies generated with the /clr (Common Language Runtime Compilation) compiler option that contain both managed and unmanaged functionality.

Using a Windows Form User Control in MFC
Discusses how to use the MFC Windows Forms support classes to host Windows Forms controls within your MFC applications.

Calling Native Functions from Managed Code
Describes how non-CLR DLLs can be used from .NET applications.

See Also