Prefixing namespace names with a company name or other well-established brand avoids the possibility of two published namespaces having the same name. Use a stable, recognized technology name at the second level of a hierarchical name.
Example:
Akadia.Traffic, System.Web.UI, System.Windows.Forms
Case guidelines
Use Pascal case as a general rule, or uppercase for very small words.
Example:
System.Windows.Forms, System.Web.UI
4). Class Naming Guidelines
Naming guidelines
Use a noun or noun phrase to name a class.
Do not use a type prefix, such as C for class, on a class name.
Do not use the underscore character (_).
Case guidelines
Use Pascal case. Example:
FileStream, Button
5). Interface Naming Guidelines
Naming guidelines
Prefix interface names with the letter "I", to indicate that the type is an interface.
Do not use the underscore character (_).
Case guidelines
Use Pascal case. Example:
IServiceProvider, IFormatable
6). Parameter Naming Guidelines
Naming guidelines
Use descriptive parameter names. Parameter names should be descriptive enough that the name of the parameter and its type can be used to determine its meaning in most scenarios. To distinguish parameters from other variables the prefix "p" should be used.
Do not prefix parameter names with Hungarian type notation.
Do not use a prefix for parameter names of an event handler and exceptions.
Case guidelines
Use camel case. Example:
pTypeName, pNumberOfItems
7). Method Naming Guidelines
Naming guidelines
Use verbs or verb phrases to name methods.
Case guidelines
Use Pascal case. Example:
RemoveAll(), GetCharAt()
8). Property / Enumerations Naming Guidelines
Naming guidelines
Use a noun or noun phrase to name properties.
Do not use Hungarian notation.
Case guidelines
Use Pascal case. Example:
BackColor, NumberOfItems
9). Event Naming Guidelines
Naming guidelines
Use an EventHandler suffix on event handler names.
Specify two parameters named sender and e. The sender parameter represents the object that raised the event. The sender parameter is always of type object, even if it is possible to use a more specific type. The state associated with the event is encapsulated in an instance of an event class named "e". Use an appropriate and specific event class for the e parameter type.
Name an event argument class with the EventArgs suffix.
Case guidelines
Use Pascal case. Example:
public delegate void MouseEventHandler(object sender, MouseEventArgs e);
9). Exception Naming Guidelines
Naming guidelines
Event handlers in Visual Studio .NET tend to use an "e" parameter for the event parameter to the call. To ensure we avoid a conflict, we will use "ex" as a standard variable name for an Exception object.
Example
catch (Exception ex)
{
// Handle Exception
}
10). Constant Naming Guidelines
The names of variables declared class constants should be all uppercase with words separated by underscores. It is recommended to use a grouping naming schema.
Example (for group AP_WIN):
AP_WIN_MIN_WIDTH, AP_WIN_MAX_WIDTH, AP_WIN_MIN_HIGHT, AP_WIN_MAX_HIGHT
11). C# Primitive Type Notation