Relate coding conventions to diagnostics and editorconfig settings

[BillWagner]

This article contains a set of guidelines that have different levels of adoption across the C# community. Some are almost universal (interfaces start with a capital I). Some are more common, but not universal (starting fields with _). Some have fallen out of favor in recent times.

This page needs to be updated to reflect current styles.

Furthermore, we should categorize coding conventions to the kinds of diagnostics available:

• Compiler warnings can help developers remove potential coding mistakes. For example CS0642: Possible mistaken empty statement.
• Analyzers find other potential mistakes, including performance or security risks.
• Style can be enforced using editorconfig settings.

In addition, we should reference the preferred style used by the runtime. That's a common style seen by .NET developers browsing our source, and it's generally consistent with what we use in docs.

---

Document Details

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

• ID: 40f42506-f4a5-859a-0266-ded002056d83
• Version Independent ID: f940f2ad-e13d-4d37-6439-f8afcbc4e4c7
• Content: C# Coding Conventions
• Content Source: docs/csharp/fundamentals/coding-style/coding-conventions.md
• Product: dotnet-csharp
• Technology: csharp-fundamentals
• GitHub Login: @BillWagner
• Microsoft Alias: wiwagn

---

Associated WorkItem - 58354

[BillWagner]

While doing this work, note that this article has a recommendation that local functions should be PascalCased. That's the current recommendation, because they are methods. However, the justification is that they are "public", like classes, interfaces and structs. That justification is incorrect.

We've generally preferred PascalCasing for methods because we chose PascalCase for all methods, regardless of access. We think of local functions as functions first. The fact they their scope is local is less important for the name.