[ACCEPTED]-Difference between assigning an Action<T> method and subscribing to Action<T> event-delegates

Accepted answer

Score: 11

(As an aside, it's hard to explain things 12 when you've used the same type names twice.)

When 11 you use a public field, clients can not 10 only subscribe to events - they can also 9 completely remove other event handlers by assigning instead 8 of adding:

myClass.OnAdd = Add;

They can also invoke the handler directly:

myClass.OnAdd("foo");

Both 7 of these violate the normal pub/sub pattern, where 6 the various subscribers are isolated from 5 one another. Subscribers don't get to overwrite 4 each other's subscriptions (only add or 3 remove their own) and they don't get to 2 raise the event themselves.

For more on events 1 and delegates, see my article on the topic.

Score: 2

You can assign more than one delegates to 1 one event (thus the += operator).

Score: 0

An Event acts like a wrapper around a Delegate 3 to offer protection from reassigning/removing 2 as John has pointed out. I found this quite 1 a good read.

Source: stackoverflow.com

[ACCEPTED]-Difference between assigning an Action<T> method and subscribing to Action<T> event-delegates

Activator.CreateInstance - How to create instances of classes that have parameterized constructors

How do you use an existing variable within one or more for loops?

Inconsistency in divide-by-zero behavior between different value types

Doing a Cast Within a LINQ Query

String concatenation with or without .ToString()?

How do I compile my App.config into my exe in a VS2010 C# console app?

Removing read only attribute on a directory using C#

Is there support for a POP3 client using C# in the .Net Framework?

Can a Delegate have an optional parameter?

Why can't I put a delegate in an interface?