Skip to content

Latest commit

 

History

History
21 lines (16 loc) · 1.72 KB

native-and-dotnet-interoperability.md

File metadata and controls

21 lines (16 loc) · 1.72 KB
description title ms.date helpviewer_keywords ms.assetid
Learn more about: Native and .NET Interoperability
Native and .NET Interoperability
11/04/2016
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

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.