C# compiler options documentation should avoid "security" terminology for strong naming #25609

This page should probably be rewritten to not use the "security" terminology. With .NET Core, there's an ongoing attempt to drive home the point that strong naming is not a feature meant for security, which is why it's not at all enforced. This page is not helping with that messaging.

(HighEntropyVA is an exception; that one is actually about security.)

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 8c990f37-3995-687b-b421-3346d2ff186f
• Version Independent ID: f3a67ca1-0a4a-cc52-3ffc-ff279fc4355d
• Content: C# Compiler Options - security options
• Content Source: docs/csharp/language-reference/compiler-options/security.md
• Product: dotnet-csharp
• Technology: csharp-language-reference
• GitHub Login: @BillWagner
• Microsoft Alias: wiwagn