Skip to main content Skip to Ask Learn chat experience

This browser is no longer supported.

Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.

Download Microsoft Edge More info about Internet Explorer and Microsoft Edge

Read in English

Read in English

Share via

Facebook x.com LinkedIn Email

Note

Access to this page requires authorization. You can try signing in or changing directories.

Access to this page requires authorization. You can try changing directories.

Naming Warnings

Article
2012-11-16

In this article

Naming warnings support adherence to the naming conventions of the .NET Framework Design Guidelines.

In This Section

Compound words should be cased correctly
Do not name enum values 'Reserved'
Do not prefix enum values with type name
Events should not have before or after prefix
Flags enums should have plural names
Identifiers should be cased correctly
Identifiers should be spelled correctly
Identifiers should differ by more than case
Identifiers should have correct prefix
Identifiers should have correct suffix
Identifiers should not contain type names
Identifiers should not contain underscores
Identifiers should not have incorrect prefix
Identifiers should not have incorrect suffix
Identifiers should not match keywords
Only FlagsAttribute enums should have plural names
Parameter names should match base declaration
Parameter names should not match member names
Property names should not match get methods
Resource string compound words should be cased correctly
Resource strings should be spelled correctly
Type names should not match namespaces
Use preferred terms

Additional resources

Additional resources

In this article

en-us

Your Privacy Choices

Previous Versions
Blog
Contribute
Privacy
Terms of Use
Trademarks
© Microsoft 2025