[Expand]General Information
[Expand]WinForms Controls
[Expand]ASP.NET Controls and MVC Extensions
[Expand]ASP.NET Bootstrap Controls
[Expand]ASP.NET Core Bootstrap Controls
[Expand]WPF Controls
[Expand]Xamarin Controls
[Expand]Windows 10 App Controls
[Expand]Office File API
[Expand]Reporting
[Expand]Report and Dashboard Server
[Expand]Dashboard
[Expand]eXpressApp Framework
[Expand]eXpress Persistent Objects
[Collapse]CodeRush
  System Requirements
  Improve Performance
 [Expand]Features by Language
 [Expand]Getting Started
 [Expand]How To
 [Expand]Coding Assistance
 [Expand]Navigation and Search Tools
 [Expand]Static Code Analysis
 [Expand]Visualization Tools
 [Collapse]Code Style Assistance
  [Expand]Code Formatters
   Programming Style Rules
   Naming Conventions
  [Expand]Code Cleanup
   Remove Unused Assembly References
  [Expand]Document Formatting (C#)
   Document Formatting (XAML)
   Member Organization
   Move Member to Region
  Building Assistance
  Debugging Assistance
 [Expand]Refactoring Assistance
 [Expand]Unit Testing Assistance
 [Expand]Decompiling Tools
 [Expand]Configuration Options
 [Expand]Extensibility
[Expand]CodeRush Classic
[Expand]Cross-Platform Core Libraries
[Expand]Tools and Utilities
 End-User Documentation
View this topic on docs.devexpress.com (Learn more)

Naming Conventions

With CodeRush, you can define naming standards for each type of identifier. They will automatically apply to your code while using refactorings and code providers. Also, the code parts that do not follow naming conventions can be treated as code issues (Analyzer ID is CRR1000).

Expanded Configuration

Naming conventions are configured in the Editor | <Language> | Naming Conventions options page.

You can configure naming conventions for any identifier kind. A convention includes prefix, suffix, capitalization type and separation type.

Note

To define the snake_case naming rule, select "all lower" in the Capitalizing menu and "With Underscopes" in Separator Options.

Expanded Usage

Naming conventions are applied on code generation (Refactorings, Code Providers and Code Templates) and referenced on Static Code Analysis (in the "The name does not correspond to naming conventions" analyzer).

There are two types of naming rules: main and additional. Code generation features refer to the main rule only, whereas the static code analysis uses both main and additional rules. In other words, the new code is generated according to the main rule, and the additional rules are used (along with the main rule) to define what naming options should not be treated as code issues.

Expanded See Also

Is this topic helpful?​​​​​​​