You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note: adding a [Behavior] attribute to a handler will disregard all assembly-wide behaviors for that handler, so any global behaviors necessary must be independently added to the handler override behaviors list.
This means that, at the moment, adding a handler specific behavior overrides the assembly-wide behavior list. What do you think about, in the future, adding an AddBehavior{Before,After} attribute that would allow someone to plug a handler specific behavior into the assembly-wide ones? Food for thought but maybe even a WithoutAssemblyBehavior to remove a specific assembly-wide behavior for a handler?