Delete native AOT interop doc (#86704)

This document lives at
https://learn.microsoft.com/en-us/dotnet/core/deploying/native-aot/interop
now.

diff --git a/src/coreclr/nativeaot/docs/README.md b/src/coreclr/nativeaot/docs/README.md
index 357e4dce963cf18013d93fef29d7549b43287ace..82752be1bec7dded836ec775c8692f72cdad35f5 100644 (file)
--- a/src/coreclr/nativeaot/docs/README.md
+++ b/src/coreclr/nativeaot/docs/README.md
@@ -5,6 +5,5 @@
 - [Debugging applications](debugging.md)
 - [Optimizing applications](optimizing.md)
 - [Reflection In AOT](reflection-in-aot-mode.md)
-- [Managed/Native Interop in AOT](interop.md)
 - [Troubleshooting](troubleshooting.md)
 - [RD.xml Documentation](rd-xml-format.md)

diff --git a/src/coreclr/nativeaot/docs/interop.md b/src/coreclr/nativeaot/docs/interop.md
deleted file mode 100644 (file)
index 30ead77..0000000
--- a/src/coreclr/nativeaot/docs/interop.md
+++ /dev/null
@@ -1,58 +0,0 @@
-# Managed/Native Interop in AOT
-
-## Direct PInvoke Calls
-
-The PInvoke calls in AOT compiled binaries are bound lazily at runtime by default for better compatibility. The AOT compiler
-can be configured to generate direct calls for selected PInvoke methods that are bound during startup. The unmanaged libraries
-and entry points referenced via direct calls always have to be available at runtime, otherwise the native binary fails to start.
-
-The benefits of direct PInvoke calls are:
-- Direct PInvoke calls have *better steady state performance*
-- Direct PInvoke calls make it possible to *link the unmanaged dependencies statically*
-
-The direct PInvoke generation can be configured using `<DirectPInvoke>` items in the project file. The item name can be either `modulename`,
-which enables direct calls for all module entry points, or `modulename!entrypointname`, which enables a direct call for the specific module
-and entry point only.
-
-`<DirectPInvokeList>filename</DirectPInvokeList>` items in the project file allow specifying a list of entry points in an external file.
-This is useful when the specification of direct PInvoke calls is long and it is not practical to specify them using individual `<DirectPInvoke>`
-items. The file can contain empty lines and comments starting with `#`.
-
-Examples:
-
-```xml
-<ItemGroup>
-  <!-- Generate direct PInvoke calls for everything in __Internal -->
-  <!-- This option replicates Mono AOT behavior that generates direct PInvoke calls for __Internal -->
-  <DirectPInvoke Include="__Internal" />
-  <!-- Generate direct PInvoke calls for everything in libc (also matches libc.so on Linux or libc.dylib on macOS) --> 
-  <DirectPInvoke Include="libc" />
-  <!-- Generate direct PInvoke calls for Sleep in kernel32 (also matches kernel32.dll on Windows) -->
-  <DirectPInvoke Include="kernel32!Sleep" />
-  <!-- Generate direct PInvoke for all APIs listed in DirectXAPIs.txt -->
-  <DirectPInvokeList Include="DirectXAPIs.txt" />
-</ItemGroup>
-```
-
-### Linking
-
-To statically link against an unmanaged library, you'll need to specify `<NativeLibrary Include="filename" />` pointing to a `.lib` file on
-Windows and a `.a` file on Unix.
-
-Examples:
-
-```xml
-<ItemGroup>
-  <!-- Generate direct PInvokes for Dependency -->
-  <DirectPInvoke Include="Dependency" />
-  <!-- Specify library to link against -->
-  <NativeLibrary Include="Dependency.lib" Condition="$(RuntimeIdentifier.StartsWith('win'))" />
-  <NativeLibrary Include="Dependency.a" Condition="!$(RuntimeIdentifier.StartsWith('win'))" />
-</ItemGroup>
-```
-
-## Native Exports
-
-The native AOT compiler will export methods annotated with `UnmanagedCallersOnlyAttribute` and an explicitly specified name as
-public C entry points. This makes it possible to either dynamically or statically link the AOT compiled modules into external
-programs. More details can be found in [NativeLibrary Sample](https://github.com/dotnet/samples/tree/main/core/nativeaot/NativeLibrary/README.md).