From 89ef5f36877f6d9cdc5d20581e09ee342bbcfe4e Mon Sep 17 00:00:00 2001 From: Genevieve Warren <24882762+gewarren@users.noreply.github.com> Date: Thu, 11 Dec 2025 15:15:55 -0800 Subject: [PATCH] fix build warnings (#12134) --- .../TypeMapAssociationAttribute`1.xml | 4 ++-- xml/System.Runtime.InteropServices/TypeMapAttribute`1.xml | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/xml/System.Runtime.InteropServices/TypeMapAssociationAttribute`1.xml b/xml/System.Runtime.InteropServices/TypeMapAssociationAttribute`1.xml index b25905f4dd7..508de57003f 100644 --- a/xml/System.Runtime.InteropServices/TypeMapAssociationAttribute`1.xml +++ b/xml/System.Runtime.InteropServices/TypeMapAssociationAttribute`1.xml @@ -37,7 +37,7 @@ ## Remarks -Types used in a managed-to-unmanaged interop operation can use to define a conditional link between the source and proxy type. If the source is kept, so is the proxy type. If trimming observes an explicit allocation of the source type, the entry is inserted into the map. +Types used in a managed-to-unmanaged interop operation can use to define a conditional link between the source and proxy type. If the source is kept, so is the proxy type. If trimming observes an explicit allocation of the source type, the entry is inserted into the map. When an application is trimmed, an entry in the Proxy Type Map is included when the "source type" is referenced in one of the following ways in reachable code: @@ -62,7 +62,7 @@ Finally, if the trimming tool determines that it's impossible to retrieve a Conflicting key/value mappings are not allowed. > [!NOTE] -> The underlying format of the produced maps is implementation-defined. Different .NET form factors might use different formats. Additionally, it isn't guaranteed that the , , and attributes are present in the final image after a trimming tool has been run. +> The underlying format of the produced maps is implementation-defined. Different .NET form factors might use different formats. Additionally, it isn't guaranteed that the , , and attributes are present in the final image after a trimming tool has been run. ]]> diff --git a/xml/System.Runtime.InteropServices/TypeMapAttribute`1.xml b/xml/System.Runtime.InteropServices/TypeMapAttribute`1.xml index deb92444230..40056c9a81a 100644 --- a/xml/System.Runtime.InteropServices/TypeMapAttribute`1.xml +++ b/xml/System.Runtime.InteropServices/TypeMapAttribute`1.xml @@ -41,7 +41,7 @@ ## Remarks -Types involved in unmanaged-to-managed interop operations can be referenced in a assembly attribute that declares the external type system name, a target type, and optionally a "trim target" to determine if the target type should be included in the map. If the constructor that doesn't take a trim target is used, the entry is always emitted into the type map. +Types involved in unmanaged-to-managed interop operations can be referenced in a assembly attribute that declares the external type system name, a target type, and optionally a "trim target" to determine if the target type should be included in the map. If the constructor that doesn't take a trim target is used, the entry is always emitted into the type map. When an application is trimmed, an entry in the External Type Map is included when the "trim target" type is referenced in one of the following ways in reachable code: @@ -65,7 +65,7 @@ Many of these instructions can be passed a generic parameter. In that case, the > Conflicting key/value mappings are not allowed. > [!NOTE] -> The underlying format of the produced maps is implementation-defined. Different .NET form factors might use different formats. Additionally, it isn't guaranteed that the , , and attributes are present in the final image after a trimming tool has been run. +> The underlying format of the produced maps is implementation-defined. Different .NET form factors might use different formats. Additionally, it isn't guaranteed that the , , and attributes are present in the final image after a trimming tool has been run. ]]>