difference between Event and Delegates

Question

0.00/5 (No votes)

See more:

What is the difference between Event and Delegates. In lots of places we have to faced this question. But not from every sites we got right answer.

Posted 24-May-12 18:27pm

joti parkash

Add a Solution

Comments

Volynsky Alex 8-Aug-12 18:58pm

Please read following articles:
http://forums.iis.net/p/1174735/1967915.aspx
http://www.codeproject.com/Articles/12043/Using-Events-and-Delegates-in-C
http://www.csharp-station.com/Tutorial/CSharp/lesson14

4 solutions

Solution 4

Dear Friend,

Hope this will make you clear litte bit.

Delegates and Events Both are related.
Delegates is a function pointer which can able to store the address of any function with same prototype.
Event is a function handler which can handles or run the functions in same prototype of its delegate.
For handling events delegate is uesd.

Regards,
AP

Posted 24-May-12 23:18pm

Arunprasath Natarajan

v2

Solution 2

Event is a C# Modifier.
Delegate is a C# type.

Please refer:
C# events vs. delegates[^]

Difference between events and delegates [^]
6 important uses of Delegates and Events[^]

what is the main difference between delegate and an event in c#?
[^]
Difference between delegate and event[^]

Posted 24-May-12 18:33pm

Prasad_Kulkarni

Comments

Sergey Alexandrovich Kryukov 25-May-12 0:40am

~~Pure lie.~~ Very inaccurate. I don't mean references of course.
Please see my comments below.
--SA

Prasad_Kulkarni 25-May-12 0:52am

Then what you actually mean??

Sergey Alexandrovich Kryukov 25-May-12 1:00am

Sorry, bit event is not a modifier, not in any sense. Where did you even get it?! Just read about it. Event is always a member of some class, like a delegate instance could be. The difference it very subtle.
With delegates, you need to be careful. There are delegate types and delegate instances which are also called delegates. And the type of a delegate instance is not its corresponding delegate type (used in the declaration of a delegate variable or a member). This way, both statements you've done by yourself are incorrect, but your references are adequate and useful.
--SA

Prasad_Kulkarni 25-May-12 1:13am

I strongly disagree with your comment Pure lie
..and what you've explained here, i'll read it once then get back to you.
Might be I am wrong, but I just answered as I have used it and work'd before. I'll go through it once.

Sergey Alexandrovich Kryukov 28-May-12 19:14pm

I scratched out these unjust words after your explanation with the link, sorry for that. But I replace it with "very inaccurate" and explained why.
--SA

Prasad_Kulkarni 25-May-12 0:57am

Please see modifier (including event)[^]
I will give reference for delegates too..

Sergey Alexandrovich Kryukov 25-May-12 1:08am

Ah, I see. Microsoft here classified syntax elements this way...
First of all, I apologize and re-vote (4), but I need to explain. I agree now that your phrase is not a lie, but it does not explain anything and is highly misleading. You've quoted the page where Microsoft explained the keyword "event", but not the event itself. It says: declares event. And the event itself is some object, and its type is declared implicitly (through delegate type declaration, but event instance type is not that type), and always a member of user-defined type. Pretty complex stuff, not so easy for understanding but pretty easy in use.
--SA

Prasad_Kulkarni 25-May-12 1:36am

I am getting confused now.
I just gone through an article where they've explained that the C# event keyword is an access modifier for delegate members.. And as you're saying it is highly misleading :(

Sergey Alexandrovich Kryukov 28-May-12 19:27pm

This is exactly the point. The word event is used in several different meanings. You pointed out the word "event" as the C# keyword, but the essence of the problem is the "event" as the object in memory, and, even more fundamental, the "event" as it is understood in event-oriented programming and more general topics, something which means transition between some states (mouse key not pressed to mouse key pressed, for example). The event as the object is something used to handle events as transition events.

Focusing on the least important aspect of events among this three is misleading. From this explanation, could anyone infer some knowledge on how some hardware interrupt ends up with a call to some event handler? I think anyone would be confused if you answered "this is because the 'event' is the modifier". My first response was because I was confused myself...

I hope I explained it...
--SA

Prasad_Kulkarni 25-May-12 1:40am

Don't appologize sir, you are far more senior for me.. You've huge experience, (1 year more than my age ;) )

Sergey Alexandrovich Kryukov 28-May-12 19:20pm

I need to apologize just because in the field of Knowledge people of different age a measured be their knowledge/results and just by Truth, not by age. Thank you for conducting correct argument-based discussion, not focusing on the irrelevant personal issues.
--SA

Prasad_Kulkarni 25-May-12 0:59am

Please see the explanation here of example 1 and example too (delegate as type)[^]

Sergey Alexandrovich Kryukov 25-May-12 1:01am

I answered to it already...
--SA

Prasad_Kulkarni 25-May-12 1:14am

Net connection is bit slower here, so din't saw your comments :)

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Wendelius · Accepted Answer · 2012-05-24T18:30:00

Solution 1

I think going through this article is well worth the time: Events and Delegates simplified[^].

Posted 24-May-12 18:30pm

Wendelius

Comments

Prasad_Kulkarni 25-May-12 0:54am

My 5! Nice article..

Wendelius 31-May-12 14:12pm

Thanks :)

VJ Reddy 25-May-12 6:35am

Good reference. 5!

Wendelius 31-May-12 14:12pm

Thanks :)

Monjurul Habib 26-May-12 15:49pm

5!

Wendelius 31-May-12 14:12pm

Thanks :)

Volynsky Alex 8-Aug-12 18:56pm

+5!

Sergey Alexandrovich Kryukov · Accepted Answer · 2012-05-24T18:39:00

That's right, good explanation is hard to find, but you can infer the answer by thorough consideration of syntax, functional language description and perhaps probing them in programming.

Roughly speaking, the event instance is a special kind of delegate instance equipped with fool-proof limitations and suitable for event processing. (In last clause I used the word "event" in two different meaning, as a .NET object and as a concept of event-oriented programming in its behavioral aspect.) Also, you should be careful with delegate types and delegate instances — they are not related as a type and its instance. If you examine a delegate instance with Reflection, you will see that its type is some class encapsulating invocation list.

Please see my past answers:
Since we have multicast delegates, why do we need events?[^],
how to call keydown event on particular button click[^],
[Solved] How to add Event for C# Control[^],
A question about usercontrols, nested controls and encapsulation.[^],
WPF : How to Use Event in Custom Control[^],
Delegates and Callbacks[^],
Copying an EventHandler[^],
c# networking windows form[^].

The delegates and delegate instances are explained in depth in my article:
Dynamic Method Dispatcher[^].

Please see the section "4.1 On the Nature of Delegate Instance" referenced above.

—SA

difference between Event and Delegates

4 solutions

Solution 1

Solution 3

Solution 4

Solution 2

Add your solution here

Preview 0

Existing Members

...or Join us