"John Baro" <johnb@NOSPAMmesware.com.au> wrote in message
news:eXVlc.20664$TT.9307@news-server.bigpond.net.au...
> It appears most of the delegates in VSNET have a sender parameter and an
> eventargs parameter. Even if the eventargs parameter is empty.
> What are the benefits of following this pattern when developing my own
> delegates?
> i.e
> instead of
> public void MyDelegate(string parameter);
> we have
> public void MyDelegate(object sender, MyInheritedEventargs parameter);
> Cheers
> JB
>
>

"Klaus H. Probst" <usenet001@vbbox.com> wrote in message
news:Ocwv1LjMEHA.2388@TK2MSFTNGP09.phx.gbl...
> Consistency? It's a sort of "unwritten" standard that will be helpful if
you
> are writing things other developers accustomed to the framework use.
>
> --
> Klaus H. Probst, MVP
> http://www.vbbox.com/
>
>
> "John Baro" <johnb@NOSPAMmesware.com.au> wrote in message
> news:eXVlc.20664$TT.9307@news-server.bigpond.net.au...
> > It appears most of the delegates in VSNET have a sender parameter and an
> > eventargs parameter. Even if the eventargs parameter is empty.
> > What are the benefits of following this pattern when developing my own
> > delegates?
> > i.e
> > instead of
> > public void MyDelegate(string parameter);
> > we have
> > public void MyDelegate(object sender, MyInheritedEventargs parameter);
> > Cheers
> > JB
> >
> >
>
>