CA1715: Identifiers should have correct prefix
TypeName | IdentifiersShouldHaveCorrectPrefix |
CheckId | CA1715 |
Category | Microsoft.Naming |
Breaking Change | Breaking - when fired on interfaces. Non-breaking - when raised on generic type parameters. |
By convention, the names of certain programming elements start with a specific prefix.
Interface names should start with an uppercase 'I' followed by another uppercase letter. This rule reports violations for interface names such as 'MyInterface' and 'IsolatedInterface'.
Generic type parameter names should start with an uppercase 'T' and optionally may be followed by another uppercase letter. This rule reports violations for generic type parameter names such as 'V' and 'Type'.
Naming conventions provide a common look for libraries that target the common language runtime. This reduces the learning curve that is required for new software libraries, and increases customer confidence that the library was developed by someone who has expertise in developing managed code.
The following example shows an incorrectly named interface.
The following example fixes the previous violation by prefixing the interface with 'I'.
The following example shows an incorrectly named generic type parameter.
The following example fixes the previous violation by prefixing the generic type parameter with 'T'.