From 36f8a8d01af7b85e10b6d07bdf195abe7fb57857 Mon Sep 17 00:00:00 2001 From: eeminionn <109454414+eeminionn@users.noreply.github.com> Date: Sat, 25 Jul 2026 03:46:47 +0000 Subject: [PATCH] fix: address issue #49691 --- docs/standard/language-independence.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/standard/language-independence.md b/docs/standard/language-independence.md index c9967d7199e22..08dc38360e549 100644 --- a/docs/standard/language-independence.md +++ b/docs/standard/language-independence.md @@ -30,7 +30,7 @@ To design a component that's language independent, you only need to apply the ru > [!IMPORTANT] > The rules for CLS compliance apply only to a component's public interface, not to its private implementation. -For example, unsigned integers other than are not CLS-compliant. Because the `Person` class in the following example exposes an `Age` property of type , the following code displays a compiler warning. +For example, unsigned integers other than are not CLS-compliant. Because the `Person` class in the following example exposes an `Age` property of type , the following code displays a compiler warning. You can make the `Person` class CLS-compliant by changing the type of the `Age` property from to , which is a CLS-compliant, 16-bit signed integer. You don't have to change the type of the private `personAge` field. [!code-csharp[Conceptual.CLSCompliant#1](../../samples/snippets/csharp/VS_Snippets_CLR/conceptual.clscompliant/cs/public1.cs#1)] [!code-vb[Conceptual.CLSCompliant#1](../../samples/snippets/visualbasic/VS_Snippets_CLR/conceptual.clscompliant/vb/public1.vb#1)]