| title | description | ms.date | f1_keywords | helpviewer_keywords | author | ms.author | ||||
|---|---|---|---|---|---|---|---|---|---|---|
CA1713: Events should not have before or after prefix (code analysis) |
Learn about code analysis rule CA1713: Events should not have before or after prefix |
11/04/2016 |
|
|
gewarren |
gewarren |
| Property | Value |
|---|---|
| Rule ID | CA1713 |
| Title | Events should not have before or after prefix |
| Category | Naming |
| Fix is breaking or non-breaking | Breaking |
| Enabled by default in .NET 8 | No |
The name of an event starts with 'Before' or 'After'.
Event names should describe the action that raises the event. To name related events that are raised in a specific sequence, use the present or past tense to indicate the relative position in the sequence of actions. For example, when naming a pair of events that is raised when closing a resource, you might name it 'Closing' and 'Closed', instead of 'BeforeClose' and 'AfterClose'.
Naming conventions provide a common look for libraries that target the common language runtime. This reduces the learning curve that is required for new software libraries, and increases customer confidence that the library was developed by someone who has expertise in developing managed code.
Remove the prefix from the event name, and consider changing the name to use the present or past tense of a verb.
Do not suppress a warning from this rule.