Compound words should be cased correctly
Important This document may not represent best practices for current development, links to downloads and other resources may no longer be valid. Current recommended version can be found here. ArchiveDisclaimer

Compound words should be cased correctly







Breaking Change

Breaking- when fired on assembliesNon Breaking - when fired on type parameters

The name of an identifier contains multiple words and at least one of the words appears to be a compound word that is not cased correctly.

The name of the identifier is split into words based on the casing. Each contiguous two word combination is checked by the Microsoft spelling checker library. If 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, a number of exceptions are built into the rule, and a number of 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 required for new software libraries, and increases customer confidence that the library was developed by someone with expertise in developing managed code.

Change the name so that it is cased correctly.

It is safe to suppress a warning from this rule if both parts of the compound word are recognized by the spelling dictionary and the intent is to use two words.

© 2015 Microsoft