[docs] Sync docs with dotnet/docs-mobile@1d79b501 (#9436)

The `docs-mobile` content has been synced with dotnet/docs-mobile@1d79b50.

A `docs-mobile/binding-libs/advanced-concepts/native-library-interop.md`
file containing an overview of Native Library interop has been added.

Author: pjcollins

Documentation/docs-mobile/TOC.yml

@@ -1,6 +1,6 @@
 - name: .NET for Android
   items:
-  - name: Getting Started
+  - name: Get started
     items:
     - name: Installation
       items:
@@ -10,7 +10,7 @@
           href: getting-started/installation/net-android.md
         - name: Install dependencies
           href: getting-started/installation/dependencies.md
-  - name: Building apps
+  - name: Build apps
     items:
     - name: Build process
       href: building-apps/build-process.md
@@ -20,18 +20,50 @@
       href: building-apps/build-properties.md
     - name: Build items
       href: building-apps/build-items.md
-  - name: Features
+  - name: Fundamentals
     items:
     - name: Layout code behind
       href: features/layout-code-behind/index.md
-    - name: Maven
+  - name: Bind Java libraries
+    items:
+    - name: Overview
+      href: binding-libs/binding-java-libs/index.md
+    - name: Bind a Java library
+      href: binding-libs/binding-java-libs/binding-java-library.md
+    - name: Bind a Java library from Maven
+      href: binding-libs/binding-java-libs/binding-java-maven-library.md
+    - name: Migrate a Xamarin.Android bindings project
+      href: /dotnet/maui/migration/android-binding-projects?toc=/dotnet/android/toc.json&bc=/dotnet/breadcrumb/android/toc.json
+    - name: Customize bindings
+      items:
+      - name: Overview
+        href: binding-libs/customizing-bindings/index.md
+      - name: Customize namespaces
+        href: binding-libs/customizing-bindings/namespace-customization.md
+      - name: Java bindings metadata
+        href: binding-libs/customizing-bindings/java-bindings-metadata.md
+      - name: Create enumerations
+        href: binding-libs/customizing-bindings/creating-enums.md
+    - name: MSBuild reference
+      items:
+      - name: MSBuild bindings project properties
+        href: binding-libs/msbuild-reference/build-properties.md
+      - name: MSBuild bindings project items
+        href: binding-libs/msbuild-reference/build-items.md
+    - name: Advanced concepts
       items:
-      - name: "@(AndroidMavenLibrary) build item"
-        href: features/maven/android-maven-library.md
-      - name: Resolving Java ependencies
-        href: features/maven/resolving-java-dependencies.md
+      - name: AndroidMavenLibrary reference
+        href: binding-libs/advanced-concepts/android-maven-library.md
       - name: Java dependency verification
-        href: features/maven/java-dependency-verification.md
+        href: binding-libs/advanced-concepts/java-dependency-verification.md
+      - name: Resolve Java dependencies
+        href: binding-libs/advanced-concepts/resolving-java-dependencies.md
+      - name: Distribute bindings libraries
+        href: binding-libs/advanced-concepts/distributing.md
+      - name: Native Library Interop
+        href: binding-libs/advanced-concepts/native-library-interop.md
+    - name: Troubleshoot bindings
+      href: binding-libs/customizing-bindings/troubleshooting-bindings.md
   - name: Message reference
     items:
     - name: Overview
@@ -296,6 +328,8 @@
         href: messages/xa4247.md
       - name: XA4248
         href: messages/xa4248.md
+      - name: XA4249
+        href: messages/xa4249.md
       - name: XA4301
         href: messages/xa4301.md
       - name: XA4302

Documentation/docs-mobile/features/maven/android-maven-library.md renamed to Documentation/docs-mobile/binding-libs/advanced-concepts/android-maven-library.md

@@ -1,13 +1,13 @@
 ---
 title: AndroidMavenLibrary Build Action .NET for Android
 description: AndroidMavenLibrary Build Action .NET for Android
-ms.date: 04/11/2024
+ms.author: jopobst
+ms.date: 05/11/2024
 ---
 # AndroidMavenLibrary
 
-Note: This feature is only available in .NET 9+.
-
-## Description
+> [!NOTE]
+> This feature is only available in .NET 9+.
 
 `<AndroidMavenLibrary>` allows a Maven artifact to be specified which will automatically be downloaded and added to a .NET for Android binding project. This can be useful to simplify maintenance of .NET for Android bindings for artifacts hosted in Maven.
 
@@ -24,7 +24,7 @@ Note: This feature is only available in .NET 9+.
 
 This will do several things at build time:
 - Download the Java [artifact](https://central.sonatype.com/artifact/com.squareup.okhttp3/okhttp/4.9.3) with group id `com.squareup.okhttp3`, artifact id `okhttp`, and version `4.9.3` from [Maven Central](https://central.sonatype.com/) to a local cache (if not already cached).
-- Add the cached package to the .NET for Android bindings build as an [`<AndroidLibrary>`](../../building-apps/build-items.md#androidlibrary).
+- Add the cached package to the .NET for Android bindings build as an [`<AndroidLibrary>`](../msbuild-reference/build-items.md#androidlibrary).
 - Download the Java artifact's POM file (and any needed parent/imported POM files) to enable [Java Dependency Verification](java-dependency-verification.md). To opt out of this feature, add `VerifyDependencies="false"` to the `<AndroidMavenLibrary>` item.
 
 Note that only the requested Java artifact is added to the .NET for Android bindings build. Any artifact dependencies are not added. If the requested artifact has dependencies, they must be fulfilled individually.
@@ -53,7 +53,7 @@ Supported values are `Central` (default), `Google`, or a URL to another Maven re
 </ItemGroup>
 ```
 
-Additionally, any attributes applied to the `<AndroidMavenLibrary>` element will be copied to the `<AndroidLibrary>` it creates internally.  Thus, [attributes](https://github.com/xamarin/xamarin-android/blob/main/Documentation/guides/OneDotNetEmbeddedResources.md#msbuild-item-groups) like `Bind` and `Pack` can be used to control the binding process. (Both default to `true`.)
+Additionally, any attributes applied to the `<AndroidMavenLibrary>` element will be copied to the `<AndroidLibrary>` it creates internally.  Thus, [attributes](../msbuild-reference/build-items.md#androidlibrary) like `Bind` and `Pack` can be used to control the binding process. (Both default to `true`.)
 
 ```xml
 <ItemGroup>

Documentation/docs-mobile/binding-libs/advanced-concepts/distributing-images/distributing-images-01.png

@@ -0,0 +1,99 @@
+---
+title: Distributing bindings libraries
+description: Once a Java library has been bound, it may be desirable to distribute it internally or via NuGet for consumption.
+ms.author: jopobst
+ms.date: 05/08/2024
+---
+
+# Distributing bindings libraries
+
+Once a Java library has been bound to be used in .NET for Android, there
+are multiple ways it can be consumed:
+
+- **Project Reference** - If the binding project and the application project
+  are in the same solution file, using a `<ProjectReference>` is generally 
+  the easiest way to consume the binding.
+  
+- **NuGet Package** - A NuGet package is ideal for public publishing or for
+  an internal distributed development environment that has an internal NuGet
+  server.
+  
+- **File Reference** - A consuming application can directly add a `<Reference>`
+  to a binding `.dll` if neither the binding project nor a NuGet server is
+  available.
+  
+## Controlling binding and packaging options
+
+A bindings library project has two options for controlling if an `<AndroidLibrary>`
+gets bound and gets redistributed:
+
+- **Bind** (`true`/`false`) - Defaults to `true`, meaning managed bindings are
+created for the specified `<AndroidLibrary>`.  Setting to `false` means the Java
+library will be included in the output, but will not have managed bindings.  This
+is useful if the library a needed dependency of another Java library, but it will
+not be called from C#.
+
+```xml
+<!-- Java library will have C# bindings and be included in the output -->
+<AndroidLibrary Include="okhttp-4.12.0.jar" />
+
+<!-- Java library will not have C# bindings but will still be included in the output -->
+<AndroidLibrary Include="okio-3.9.0.jar" Bind="false" />
+```
+
+- **Pack** (`true`/`false`) - Defaults to `true`, meaning the specified `<AndroidLibrary>`
+will be included in the output (such as a NuGet package).  Setting to `false` means the Java
+library will not be included in the output. This is a rare scenario in case the dependency is
+already being provided via alternative means.
+
+```xml
+<!-- Java library will have C# bindings and be included in the output -->
+<AndroidLibrary Include="okhttp-4.12.0.jar" />
+
+<!-- Java library will have C# bindings but will *not* be included in the output -->
+<AndroidLibrary Include="okio-3.9.0.jar" Pack="false" />
+```
+
+## ProjectReference
+
+If the binding project and the application project are in the same solution file, 
+using a `<ProjectReference>` is generally the easiest way to consume the binding:
+
+```xml
+<ProjectReference Include="mybindinglib.csproj" />
+```
+
+The build system will be responsible for adding the managed bindings as well as any
+`.jar`/`.aar` files to the application project.
+
+## NuGet package
+
+As a property inherited from .NET SDK-style projects, any bindings library can be
+trivially packaged into a redistributable NuGet package by using the "Pack" command
+in Visual Studio or from the command line:
+
+```dotnetcli
+dotnet pack
+```
+
+The bindings library as well as the Java library will be included in the NuGet package:
+
+![NuGet package contents](distributing-images/distributing-images-01.png)
+
+Use the `Pack` attribute documented above to control which Java libraries are desired
+in the NuGet package.
+
+NuGet packages can be customized using the [standard .NET MSBuild elements](/nuget/create-packages/creating-a-package-dotnet-cli#set-properties).
+
+## File reference
+
+If neither of the above options are possible, the binding `.dll` can be referenced
+directly with a `<Reference>` element. Note that any Java libraries that are part
+of the binding project output must be in the **same directory** as the binding `.dll`.
+
+If you move/copy just the binding `.dll` to another location and do not also move/copy
+any `.jar`/`.dll` files they will not end up in your application and the binding will
+fail at runtime.
+
+> [!IMPORTANT]
+> In Classic Xamarin.Android using an item action like `EmbeddedJar` would place the `.jar` file inside the `.dll` and only one file would be needed. Support for this was removed in .NET for Android because it greatly increased application build time to scan and extract embedded Java library files. Any needed `.jar`/`.dll` files MUST be located in the same directory as the binding `.dll`.

Documentation/docs-mobile/binding-libs/advanced-concepts/distributing.md

@@ -1,19 +1,21 @@
 ---
 title: Java Dependency Verification in .NET for Android
 description: Java Dependency Verification in .NET for Android
-ms.date: 04/11/2024
+ms.author: jopobst
+ms.date: 05/11/2024
 ---
-# Java Dependency Verification
 
-Note: This feature is only available in .NET 9+.
+# Java dependency verification
 
-## Description
+> [!NOTE]
+> This feature is only available in .NET 9+.
 
 A common problem when creating Java binding libraries for .NET for Android is not providing the required Java dependencies. The binding process ignores API that requires missing dependencies, so this can result in large portions of desired API not being bound.
 
 Unlike .NET assemblies, a Java library does not specify its dependencies in the package. The dependency information is stored in external files called POM files. In order to consume this information to ensure correct dependencies an additional layer of files must be added to a binding project.
 
-Note: the preferred way of interacting with this system is to use [`<AndroidMavenLibrary>`](android-maven-library.md) which will automatically download any needed POM files.
+> [!TIP]
+> The preferred way of interacting with this system is to use [`<AndroidMavenLibrary>`](android-maven-library.md) which will automatically download any needed POM files.
 
 For example:
 
@@ -27,13 +29,11 @@ automatically gets expanded to:
 <AndroidLibrary 
   Include="<MavenCacheDir>/Central/com.squareup.okio/okio/1.17.4/com.squareup.okio_okio.jar" 
   Manifest="<MavenCacheDir>/Central/com.squareup.okio/okio/1.17.4/com.squareup.okio_okio.pom"
-  JavaArtifact="com.squareup.okio:okio" 
-  JavaVersion="1.17.4" />
+  JavaArtifact="com.squareup.okio:okio:1.17.4" />
 
 <AndroidAdditionalJavaManifest
   Include="<MavenCacheDir>/Central/com.squareup.okio/okio-parent/1.17.4/okio-parent-1.17.4.pom"
-  JavaArtifact="com.squareup.okio:okio-parent"
-  JavaVersion="1.17.4" />
+  JavaArtifact="com.squareup.okio:okio-parent:1.17.4" />
 
 etc.
 ```
@@ -42,16 +42,15 @@ However it is also possible to manually opt in to Java dependency verification u
 
 ## Specification
 
-To manually opt in to Java dependency verification, add the `Manifest`, `JavaArtifact`, and `JavaVersion` attributes to an `<AndroidLibrary>` item:
+To manually opt in to Java dependency verification, add the `Manifest` and `JavaArtifact` attributes to an `<AndroidLibrary>` item:
 
 ```xml
-<!-- JavaArtifact format is {GroupId}:{ArtifactId} -->
+<!-- JavaArtifact format is {GroupId}:{ArtifactId}:{Version} -->
 <ItemGroup>
   <AndroidLibrary
     Include="my_binding_library.jar"
     Manifest="my_binding_library.pom"
-    JavaArtifact="com.example:mybinding"
-    JavaVersion="1.0.0" />
+    JavaArtifact="com.example:mybinding:1.0.0" />
 </ItemGroup>
 ```
 
@@ -65,7 +64,7 @@ error : Java dependency 'androidx.collection:collection' version '1.0.0' is not
 
 Seeing these error(s) or no errors should indicate that the Java dependency verification is working. Follow the [Resolving Java Dependencies](resolving-java-dependencies.md) guide to fix any missing dependency errors.
 
-## Additional POM Files
+## Additional POM files
 
 POM files can sometimes have some optional features in use that make them more complicated than the above example.
 
@@ -104,12 +103,11 @@ error : Unable to resolve POM for artifact 'com.squareup.okio:okio-parent:1.17.4
 In this case, we need to provide the POM file for `com.squareup.okio:okio-parent:1.17.4`:
 
 ```xml
-<!-- JavaArtifact format is {GroupId}:{ArtifactId} -->
+<!-- JavaArtifact format is {GroupId}:{ArtifactId}:{Version} -->
 <ItemGroup>
   <AndroidAdditionalJavaManifest
     Include="com.square.okio.okio-parent.1.17.4.pom"
-    JavaArtifact="com.squareup.okio:okio-parent"
-    JavaVersion="1.17.4" />
+    JavaArtifact="com.squareup.okio:okio-parent:1.17.4" />
 </ItemGroup>
 ```
 

Documentation/docs-mobile/features/maven/java-dependency-verification.md renamed to Documentation/docs-mobile/binding-libs/advanced-concepts/java-dependency-verification.md

@@ -0,0 +1,32 @@
+---
+title: AndroidMavenLibrary Build Action .NET for Android
+description: AndroidMavenLibrary Build Action .NET for Android
+ms.date: 10/21/2024
+---
+# NativeLibraryInterop
+
+## Overview
+Native Library Interop (formerly referred to as the "Slim Binding" approach), refers to a
+pattern for accessing native SDKs in .NET for Android and .NET MAUI projects.
+
+Starting in .NET 9, the .NET for Android SDK supports building Gradle projects
+by using the `@(AndroidGradleProject)` build action. This is declared in
+an MSBuild ItemGroup in a project file:
+
+```xml
+<ItemGroup>
+  <AndroidGradleProject Include="path/to/project/build.gradle.kts" ModuleName="mylibrary" />
+</ItemGroup>
+```
+
+When an `@(AndroidGradleProject)` item is added to a .NET for Android project, the build process
+will attempt to create an AAR or APK file from the specified Gradle project. Any AAR output files
+will be added to the .NET project as an `@(AndroidLibrary)` to be bound.
+
+Please see the [build-items](../../building-apps/build-items.md) docs for more information about
+the `@(AndroidGradleProject)` build action.
+
+Additional documentation and references can be found below:
+
+* https://learn.microsoft.com/en-us/dotnet/communitytoolkit/maui/native-library-interop
+* https://github.com/CommunityToolkit/Maui.NativeLibraryInterop