Tim,

>I find it important to stick to a reasonable naming convention and try to do this with my code. I am using a what I thought was consistent with Microsoft regarding events such as
>
>// the event
>public event CustomerChangedDelegate CustomerChanged
>
>// Event args
>public class CustomerChangedEventArgs : EventArgs
>
>// the method that raises the event (In the publisher)
>public void OnCustomerChanged()
>
>// The method for the handler (at the subscriber)
>public void CustomerChangedHandler()
>
>Why then with every book I look at are these same names being used but differently such as
>public void OnCustomerChanged() used as the handler method at the subscriber. or
>public event CustomerChanged OnCustomerChanged when creating the event

I've seen some code samples like this and you're right...it's simply bad naming conventions. The conventions you are using are similar to what Microsoft is using, except for the naming of the delegate. Sadly, Microsoft often names the delegate with a "Handler" suffix, obfuscating the fact that it is a handler (just double click on any Windows Forms user interface control and examine the registration code behind the scenes and you'll see what I mean). I personally advocate the naming convention you are using because it's clear that a delegate is a delegate.

Best Regards,