Could you elaborate on that? The problem is that I already have multiple implementations for some of the services (which is: the ones that do have names; and therefore cause problems with this approach) - and they're named so I can use a custom IHandlerSelector to pick the right one for a given job (which, in some cases, even includes a composite services that gets two other ones to merge their results together). Plus, I do not register them both in Code with an Installer (which would work!), but I register one of them in the Config and the other from Code (which is why I'm confused on how one of them can work but the other behaves differently).
The only way I could see this work is by using a different name for the updated component that follows some sort of convention (like "Override" + the original name), so the IHandlerSelector could do its thing...and, actually, writing about it does make sense! I'll give that a try once I find some free time to do so. Thanks! On Friday, October 14, 2016 at 9:43:08 AM UTC+2, Ken Egozi wrote: > > A cleaner (and possibly clearer) way to achieve an override ability is to > use a custom IHandlerSelector, in which you can pick an override if it > exist. > > Ken Egozi. > http://kenegozi.com/ <http://kenegozi.com/blog> > -- You received this message because you are subscribed to the Google Groups "Castle Project Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/castle-project-users. For more options, visit https://groups.google.com/d/optout.
