Confussed about parameters for Events

[news.microsoft.com]

In one of my books called "Mastering C#" there is a statement that reads
"All event handler delegates must return void and accept two parameters. The
first parameter is an object, and it represents the object that raises the
event... The second is a parameter that is an object of a class derived from
the System.EventArg s class".

Now I know that this can not be true in general because I have created
events that do not match these parameters. I know there are some system
delegates that are designed to be used with event handers that are defined
with this signiture and using one of those would require the appropriate
parameters to be passed to it.

I just though maybe I was missing something and thought if anyone can
clarify things, that would be great!.

Thanks for your help

Earl

[Philip Rieck]

The book is either in error or out of context...

(almost?) all of the event handler delegates in the FCL use this signature,
but it is not a requirement -- rather it is a guideline.

public delegate void SomeEventHandle r( object sender,
MyClassThatInhe ritsFromEventAr gs e);
....
public event SomeEventHandle r SomeEvent;

This is the preferred pattern for events. However, it's not required. Just
as valid would be
public delegate int SomeEventHandle r( int x, int y);
....
public event SomeEventHandle r SomeEvent;

Now, ignoring statndards and best practices is done at your own risk, but
there's no technical reason you can't do the last one.

The nice thing about using the first example is that if someone didn't care
for the extended information in the second parameter, they could use
System.EventHan dler delegates and hook up to your events blindly. But
again, not a requirement, just a strong guideline.
"news.microsoft .com" <ea******@hotma il.com> wrote in message
news:uC******** ******@TK2MSFTN GP12.phx.gbl...

In one of my books called "Mastering C#" there is a statement that reads
"All event handler delegates must return void and accept two parameters. The first parameter is an object, and it represents the object that raises the
event... The second is a parameter that is an object of a class derived from the System.EventArg s class".

Now I know that this can not be true in general because I have created
events that do not match these parameters. I know there are some system
delegates that are designed to be used with event handers that are defined
with this signiture and using one of those would require the appropriate
parameters to be passed to it.

I just though maybe I was missing something and thought if anyone can
clarify things, that would be great!.

Thanks for your help

Earl

[news.microsoft.com]

Philip, thanks for the reply. I read the entire chapter so I don't think I
got anything out of context. Overall Mastering C# is a very good and easy to
understand book but I guess the author missed on this one. No more
confussion on my part. Thanks

Earl

"Philip Rieck" <st***@mckraken .com> wrote in message
news:Oj******** ******@TK2MSFTN GP09.phx.gbl...

The book is either in error or out of context...

(almost?) all of the event handler delegates in the FCL use this signature, but it is not a requirement -- rather it is a guideline.

public delegate void SomeEventHandle r( object sender,
MyClassThatInhe ritsFromEventAr gs e);
...
public event SomeEventHandle r SomeEvent;

This is the preferred pattern for events. However, it's not required. Just as valid would be
public delegate int SomeEventHandle r( int x, int y);
...
public event SomeEventHandle r SomeEvent;

Now, ignoring statndards and best practices is done at your own risk, but
there's no technical reason you can't do the last one.

The nice thing about using the first example is that if someone didn't care for the extended information in the second parameter, they could use
System.EventHan dler delegates and hook up to your events blindly. But
again, not a requirement, just a strong guideline.
"news.microsoft .com" <ea******@hotma il.com> wrote in message
news:uC******** ******@TK2MSFTN GP12.phx.gbl...

In one of my books called "Mastering C#" there is a statement that reads
"All event handler delegates must return void and accept two parameters.

The

first parameter is an object, and it represents the object that raises the event... The second is a parameter that is an object of a class derived

from

the System.EventArg s class".

Now I know that this can not be true in general because I have created
events that do not match these parameters. I know there are some system
delegates that are designed to be used with event handers that are defined with this signiture and using one of those would require the appropriate
parameters to be passed to it.

I just though maybe I was missing something and thought if anyone can
clarify things, that would be great!.

Thanks for your help

Earl

[Jay B. Harlow [MVP - Outlook]]

Earl,
As Philip suggested it is a guideline, that is worth following.

For details on the Guideline see:

http://msdn.microsoft.com/library/de...Guidelines.asp

http://msdn.microsoft.com/library/de...Guidelines.asp

Hope this helps
Jay

"news.microsoft .com" <ea******@hotma il.com> wrote in message
news:uC******** ******@TK2MSFTN GP12.phx.gbl...

In one of my books called "Mastering C#" there is a statement that reads
"All event handler delegates must return void and accept two parameters. The first parameter is an object, and it represents the object that raises the
event... The second is a parameter that is an object of a class derived from the System.EventArg s class".

Now I know that this can not be true in general because I have created
events that do not match these parameters. I know there are some system
delegates that are designed to be used with event handers that are defined
with this signiture and using one of those would require the appropriate
parameters to be passed to it.

I just though maybe I was missing something and thought if anyone can
clarify things, that would be great!.

Thanks for your help

Earl

[Earl Teigrob]

Jay,

I have normally used these conventions because the books I have read have
done them this way, but it is great to have the official recommedations. ..
Thanks...

Earl
"Jay B. Harlow [MVP - Outlook]" <Ja************ @msn.com> wrote in message
news:%2******** **********@TK2M SFTNGP11.phx.gb l...

Earl,
As Philip suggested it is a guideline, that is worth following.

For details on the Guideline see:

http://msdn.microsoft.com/library/de...Guidelines.asp
http://msdn.microsoft.com/library/de...Guidelines.asp
Hope this helps
Jay

"news.microsoft .com" <ea******@hotma il.com> wrote in message
news:uC******** ******@TK2MSFTN GP12.phx.gbl...

In one of my books called "Mastering C#" there is a statement that reads
"All event handler delegates must return void and accept two parameters.

The

first parameter is an object, and it represents the object that raises the event... The second is a parameter that is an object of a class derived

from

the System.EventArg s class".

Now I know that this can not be true in general because I have created
events that do not match these parameters. I know there are some system
delegates that are designed to be used with event handers that are defined with this signiture and using one of those would require the appropriate
parameters to be passed to it.

I just though maybe I was missing something and thought if anyone can
clarify things, that would be great!.

Thanks for your help

Earl