"Larry Minton" <avguard@jadeinc.com> wrote in message
news:g0is42tnkp0ejnuci31mmbon2quif0t58j@4ax.com...
> Is there a way to tell via reflection whether a class does not support
> an event/method/property defined in a base class? For example,
> consider:
>
> WebBrowser Events:
> Event: Click
> Description: This event is not supported by this control. (Inherited
> from WebBrowserBase)
>
> We are automatically hooking up event handlers to events, and are
> getting System.NotSupportedException exceptions when trying to hook up
> to such events. So far, I haven't been able to figure out a way to
> exclude these types of events.
>
> Thanks,
> Larry

"Greg Young [MVP]" <DruckDruckGoose@hotmail.com> wrote in message
news:uLoaO2MaGHA.4612@TK2MSFTNGP03.phx.gbl...
> No as a general rule there is no good way to do this unless thought is put
> in ahead of time to either place a "NonImplementedAttribute" or to have an
> interface which defines whether or not functionalities are available (i.e.
> Stream.CanSeek)
>

>
> "Larry Minton" <avguard@jadeinc.com> wrote in message
> news:g0is42tnkp0ejnuci31mmbon2quif0t58j@4ax.com...
>> Is there a way to tell via reflection whether a class does not support
>> an event/method/property defined in a base class? For example,
>> consider:
>>
>> WebBrowser Events:
>> Event: Click
>> Description: This event is not supported by this control. (Inherited
>> from WebBrowserBase)
>>
>> We are automatically hooking up event handlers to events, and are
>> getting System.NotSupportedException exceptions when trying to hook up
>> to such events. So far, I haven't been able to figure out a way to
>> exclude these types of events.
>>
>> Thanks,
>> Larry
>
>

>Of course catching a NotSupportedException is far more efficient than
>reflection, potentially even more efficient than checking a return value
>because exception handling is outside the critical path.