Menu
I'm wondering why should I use a class that inherits from the EventArgs class instead of using a custom class that will do the same job for me when passing event data?
598
AssemblyLoadEventArgs class derives from EventArgs and is used to hold the data for assembly load events. To create a custom event data class, create a class that derives from the EventArgs class and provide the properties to store the necessary data. The name of your custom event data class should end with EventArgs .
EventArgs e is a parameter called e that contains the event data, see the EventArgs MSDN page for more information. Object Sender is a parameter called Sender that contains a reference to the control/object that raised the event. Event Arg Class: http://msdn.microsoft.com/en-us/library/system.eventargs.aspx.
You don't have to inherit from EventArgs, but it allows people using your classes to use and handle generic *Handler(object sender, EventArgs e) declarations. If you don't inherit from EventArgs, then they have to use explicitly typed
*Handler(object sender, YairsFakeEventArgs e) The same goes for just using custom delegates but they are a lot more explicitly different.
153
Because your event-args class will be compatible with any other function that accepts an EventArgs object.
20
Because that's what would be the standard and most idiomatic way to do this in .NET. The whole ASP.NET and WinForms event model relies on those conventions. If another developer reads your code he will more easily understand it as this is the standard. This being said you could of course use any class you like.
31
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
