I originally wrote the article using a delegate instead of the EventHandler and didn’t think to go the whole hog when changing over.

Thanks for the pickup.

public event EventHandler AutomobileChangeHandler;

This also saves you from having to explicitly create a property for the AutomobileChangeHandler.

The reason that you’re supposed to do it like this is because the “event” keyword hides the complexity of event registration and de-registration. But, you can explicitly implement your own storage mechanism for event handlers, similar to how you create a property – except instead of “get” and “set”, you use “add” and “remove” –

private IList handlers = new List();
public event EventHandler AutomobileChangeHandler {
    add {  handlers.Add(value); }
    remove { handlers.Remove(value); }
}

Obviously, using the += and -= notation is the shorthand way of calling the add and remove properties of an event.