Native and .NET Interoperability

This page is specific to

Microsoft Visual Studio 2008/.NET Framework 3.5

Other versions are also available for the following:

Visual C++

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 Native COM Servers from .NET: Describes how COM components can be used from .NET applications.
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.

Other Resources

Common Programming Methodologies

Tags

: Add a tag

Community Content

Add new content

Annotations

Other .NET Interoperability Resources

orcmid ... Thomas Lee | Edit | Show History

I've been gathering links to .NET Interoperability resources to support those who are attempting to use C++/CLI to bridge to and from .NET for integration with other software and products. I'd like to see more about connecting the dots and I have a start on the Interoperability Forums at this thread:
http://forums.community.microsoft.com/en-US/interopscenarios/thread/662dc344-c874-4f22-9c43-89c8fe578e7f

What other places have people found useful resources and examples on interop?