There’s a question about why interfaces dont let you add event definitions to them.<\/p>\n\n\n\n
In fact since they just define a signature and leave the implementation else where I suppose they could. There’s no real compelling reason they couldn’t that I can think of.<\/p>\n\n\n\n
They just don’t.<\/p>\n\n\n\n
And so in the mean time what do you do ? How can you have the effect of an event without being able to define one ?<\/p>\n\n\n\n
What you can do is define a method on the interface that takes a delegate and then implementors can call that delegate back at appropriate times – much like you’d do with raising an event.<\/p>\n\n\n\n
The upside to using an interface is that you CAN apply it to disparate items – they dont have to all inherit from the same base class or control.<\/p>\n\n\n\n
The downside is that its not an event so you can use addhandler to handle it. To be quite frank some of the bugs I’ve seen over the years suggest that AddHandler is overused. <\/p>\n\n\n\n
<\/p>\n","protected":false},"excerpt":{"rendered":"
There’s a question about why interfaces dont let you add event definitions to them. In fact since they just define a signature and leave the implementation else where I suppose they could. There’s no real compelling reason they couldn’t that I can think of. They just don’t. And so in the mean time what do … <\/p>\n