Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
In .NET 11, Mono embedding APIs are no longer supported on mobile platforms.
Version introduced
.NET 11
Previous behavior
Native code could embed Mono by using Mono header files, linking to
libmonosgen-2.0, and calling mono_* APIs. These APIs exposed runtime,
domain, metadata, object, method-call, GC-handle, internal-call, thread, and
profiling features.
New behavior
Mono embedding APIs are no longer supported. CoreCLR on mobile platforms doesn't provide a direct replacement for the Mono embedding API.
This change doesn't affect normal P/Invoke, LibraryImportAttribute, Java interop, or Objective-C interop.
Type of breaking change
This change is source incompatible, binary incompatible, and a behavioral change.
Reason for change
Mono and CoreCLR use different hosting and embedding interfaces.
Recommended action
- Follow native interoperability best practices.
- Use UnmanagedCallersOnlyAttribute and C# function pointers for native-to-managed callbacks.
- Use values that have the same layout in managed and native code (blittable values).
- Consider moving performance-critical, chatty managed/native interfaces to a fully managed implementation to reduce interop overhead.
Affected APIs
- The Mono native embedding API, including
mono_*functions andlibmonosgen-2.0.
Collaborate with us on GitHub
The source for this content can be found on GitHub, where you can also create and review issues and pull requests. For more information, see our contributor guide.
