Home/ Questions/Q 8061911
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-05T10:29:41+00:00

When I declare an event, I’ve been using the Action delegate or Action<T, …>

  • 0

When I declare an event, I’ve been using the Action delegate or Action<T, ...> delegate if the event handler has parameters. I recently noticed the existence of the EventHandler delegate, which requires a type param that inherits EventArgs. The latter method requires that I create an additional class that exists only to encapsulate whatever parameters are passed with the event, which seems unnecessary, unless I’m missing something.

So, what are the reasons for using the EventArgs delegate when declaring an event? What does it buy me?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    It buys you the ability to return event arguments, that’s all. If you have no need for that, then maybe you don’t need an EventHandler delegate.

    From a larger perspective, EventArgs is the “socially acceptable” way of getting data from one place to another using events. You can create custom delegates to do this, of course, but EventArgs has tooling support in Visual Studio, etc.

    • 0