Skip to content

Commit 89ef5f3

Browse files
authored
fix build warnings (#12134)
1 parent 1bf1fcd commit 89ef5f3

File tree

2 files changed

+4
-4
lines changed

2 files changed

+4
-4
lines changed

xml/System.Runtime.InteropServices/TypeMapAssociationAttribute`1.xml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -37,7 +37,7 @@
3737
3838
## Remarks
3939
40-
Types used in a managed-to-unmanaged interop operation can use <xref:System.Runtime.InteropServices.TypeMapAssociationAttribute%60%601> 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.
40+
Types used in a managed-to-unmanaged interop operation can use <xref:System.Runtime.InteropServices.TypeMapAssociationAttribute`1> 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.
4141
4242
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:
4343
@@ -62,7 +62,7 @@ Finally, if the trimming tool determines that it's impossible to retrieve a <xre
6262
> Conflicting key/value mappings are not allowed.
6363
6464
> [!NOTE]
65-
> 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 <xref:System.Runtime.InteropServices.TypeMapAttribute%60%601>, <xref:System.Runtime.InteropServices.TypeMapAssociationAttribute%60%601>, and <xref:System.Runtime.InteropServices.TypeMapAssemblyTarget%60%601> attributes are present in the final image after a trimming tool has been run.
65+
> 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 <xref:System.Runtime.InteropServices.TypeMapAttribute`1>, <xref:System.Runtime.InteropServices.TypeMapAssociationAttribute`1>, and <xref:System.Runtime.InteropServices.TypeMapAssemblyTargetAttribute`1> attributes are present in the final image after a trimming tool has been run.
6666
6767
]]></format>
6868
</remarks>

xml/System.Runtime.InteropServices/TypeMapAttribute`1.xml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -41,7 +41,7 @@
4141
4242
## Remarks
4343
44-
Types involved in unmanaged-to-managed interop operations can be referenced in a <xref:System.Runtime.InteropServices.TypeMapAttribute%60%601> 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.
44+
Types involved in unmanaged-to-managed interop operations can be referenced in a <xref:System.Runtime.InteropServices.TypeMapAttribute`1> 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.
4545
4646
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:
4747
@@ -65,7 +65,7 @@ Many of these instructions can be passed a generic parameter. In that case, the
6565
> Conflicting key/value mappings are not allowed.
6666
6767
> [!NOTE]
68-
> 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 <xref:System.Runtime.InteropServices.TypeMapAttribute%60%601>, <xref:System.Runtime.InteropServices.TypeMapAssociationAttribute%60%601>, and <xref:System.Runtime.InteropServices.TypeMapAssemblyTarget%60%601> attributes are present in the final image after a trimming tool has been run.
68+
> 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 <xref:System.Runtime.InteropServices.TypeMapAttribute`1>, <xref:System.Runtime.InteropServices.TypeMapAssociationAttribute`1>, and <xref:System.Runtime.InteropServices.TypeMapAssemblyTargetAttribute`1> attributes are present in the final image after a trimming tool has been run.
6969
7070
]]></format>
7171
</remarks>

0 commit comments

Comments
 (0)