ninject / ninject.extensions.weakeventmessagebroker Goto Github PK

When annotating methods on classes that extend Control or DispatcherObject it would be really nice if there was a way to mark the methods as requiring Invoke to be called. At present one has to add boiler plate to each subscription to check InvokeRequire and then Invoke if appropriate.

E.g. [Subscribe("message://UpdateAvailable", Invoke=true)]

The broker could check the MethodInfo's declaring class and if extends Control or DispatcherObject it could delegate to the Invoke call. It might even be nice to have a second property "ASync" which would call the events using BeginInvoke.

On this theme a flag to specify that the event should be run on the ThreadPool could also be useful.

Is this feasible?

At present if you try to subscribe to a MessageChannel with the incorrect method signature you'll receive an InvalidProgramException: JIT Compiler encountered an internal limitation.

The MessageChannel could check when an event/method is registered that the method matches the form required. e.g. void EventHandler(object sender, EventArgs args).

A further extension to this would be to record the first method/event signature registered for a channel and to check all subsequent registrations match the first and throw a descriptive ActivationException if not.

N.B when compiled with NO_LCG the reflection based transport will throw a more informative exception about the method signatures having different numbers of parameters.