event Action vs event EventHandler

by

Based on some of the previous answers, I’m going to break my answer down into three areas.

First, physical limitations of using Action<T1, T2, T2... > vs using a derived class of EventArgs. There are three: First, if you change the number or types of parameters, every method that subscribes to will have to be changed to conform to the new pattern. If this is a public facing event that 3rd party assemblies will be using, and there is any possiblity that the event args would change, this would be a reason to use a custom class derived from event args for consistencies sake (remember, you COULD still use an Action<MyCustomClass>) Second, using Action<T1, T2, T2... > will prevent you from passing feedback BACK to the calling method unless you have a some kind of object (with a Handled property for instance) that is passed along with the Action. Third, you don’t get named parameters, so if you’re passing 3 bool‘s an int, two string‘s, and a DateTime, you have no idea what the meaning of those values are. As a side note, you can still have a “Fire this event safely method while still using Action<T1, T2, T2... >“.

Secondly, consistency implications. If you have a large system you’re already working with, it’s nearly always better to follow the way the rest of the system is designed unless you have an very good reason not too. If you have publicly facing events that need to be maintained, the ability to substitute derived classes can be important. Keep that in mind.

Thirdly, real life practice, I personally find that I tend to create a lot of one off events for things like property changes that I need to interact with (Particularly when doing MVVM with view models that interact with each other) or where the event has a single parameter. Most of the time these events take on the form of public event Action<[classtype], bool> [PropertyName]Changed; or public event Action SomethingHappened;. In these cases, there are two benefits. First, I get a type for the issuing class. If MyClass declares and is the only class firing the event, I get an explicit instance of MyClass to work with in the event handler. Secondly, for simple events such as property change events, the meaning of the parameters is obvious and stated in the name of the event handler and I don’t have to create a myriad of classes for these kinds of events.

More Related Contents:

  1. CMD command on c#
  2. What is the purpose of “return await” in C#?
  3. Creating a DPI-Aware Application
  4. Why does the EF 6 tutorial use asynchronous calls?
  5. What are the true benefits of ExpandoObject?
  6. “Invalid JSON primitive” in Ajax processing
  7. Deserializing JSON to abstract class
  8. Post parameter is always null
  9. LINQ Select Distinct with Anonymous Types
  10. Is there anything like asynchronous BlockingCollection?
  11. Creating sine or square wave in C#
  12. How to get the closest number from a List with LINQ?
  13. How to color different words with different colors in a RichTextBox while a user is writing and raise an event when that colored text is clicked
  14. How can I remove accents on a string? [duplicate]
  15. Advantages to Using Private Static Methods
  16. Is the C# compiler smart enough to optimize this code?
  17. How do I clear tracked entities in entity framework
  18. Are IEnumerable Linq methods thread-safe?
  19. How to check that a uri string is valid
  20. How do I map XML to C# objects
  21. How to I apply filter while paginating in Asp.net MVC and entity Framework?
  22. ASP.NET GridView RowIndex As CommandArgument
  23. Consume a SOAP web service without relying on the app.config
  24. Auto highlight text in a textbox control
  25. .net Framework Error (HRESULT 0x8007000B)
  26. Renaming a directory in C# [closed]
  27. C# Regex to match the word with dot
  28. Why do both the abstract class and interface exist in C#?
  29. Is it a good way of unit testing to use another, tested function to make preparations for the actual test?
  30. Parse Complex WSDL Parameter Information

Leave a Comment