Export (0) Print
Expand All

Identifiers should be cased correctly

TypeName

IdentifiersShouldBeCasedCorrectly

CheckId

CA1709

Category

Microsoft.Naming

Breaking Change

Breaking

The name of an identifier is not cased correctly.

By convention, parameter names use camel casing; namespace, type, and member names use Pascal casing. In a camel-cased name, the first letter is lower case, and the first letter of any remaining words in the name is in uppercase. Examples of camel-cased names are "packetSniffer", "ioFile", and "fatalErrorCode". In a Pascal-cased name, the first letter is upper case, and the first letter of any remaining words in the name is in uppercase. Examples of Pascal-cased names are "PacketSniffer", "IOFile", and "FatalErrorCode".

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.

Do not exclude a warning from this rule.

Community Additions

ADD
Show:
© 2014 Microsoft