This project has moved. For the latest updates, please go here.
The following rules outline the naming guidelines for events:
  • Use Pascal case.
  • Do not use Hungarian notation.
  • 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.
  • Consider naming events with a verb. For example, correctly named event names include Clicked, Painting, and DroppedDown.
  • Use a gerund (the "ing" form of a verb) to create an event name that expresses the concept of pre-event, and a past-tense verb to represent post-event. For example, a Close event that can be canceled should have a Closing event and a Closed event. Do not use the BeforeXxx/AfterXxx naming pattern.
  • Do not use a prefix or suffix on the event declaration on the type. For example, use Close instead of OnClose.
  • In general, you should provide a protected method called OnXxx on types with events that can be overridden in a derived class. This method should only have the event parameter e, because the sender is always the instance of the type.

The following example illustrates an event handler with an appropriate name and parameters.
public delegate void MouseEventHandler(object sender, MouseEventArgs e);

The following example illustrates a correctly named event argument class.
public class MouseEventArgs : EventArgs {
   public MouseEventArgs(int x, int y) { 
   this.X = x; this.Y = y; }
   public int X { get; private set; } 
   public int Y { get; private set; } 

Last edited Jul 15, 2010 at 3:45 PM by camalot, version 1