CA1702: Compound words should be cased correctly
|
TypeName |
CompoundWordsShouldBeCasedCorrectly |
|
CheckId |
CA1702 |
|
Category |
Microsoft.Naming |
|
Breaking Change |
Breaking- when fired on assemblies. Non-breaking - when fired on type parameters. |
The name of the identifier is split into words that are based on the casing. Each contiguous two-word combination is checked by the Microsoft spelling checker library. If it is recognized, the identifier produces a violation of the rule. Examples of compound words that cause a violation are "CheckSum" and "MultiPart", which should be cased as "Checksum" and "Multipart", respectively. Due to previous common usage, several exceptions are built into the rule, and several single words are flagged, such as "Toolbar" and "Filename", that should be cased as two distinct words (in this case, "ToolBar" and "FileName").
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.