difference between using ISubDependencyResolver and IHandlerSelector

[zloidooraque]

What is the fundamental difference between using ISubDependencyResolver and IHandlerSelector for acquiring components in customized way?

[Patrick Steele]

Sub Dependency Resolvers can resolve lower level parameters that may not be registered in Windsor (like a connection string).  Handler Selectors are used when you have a dependency that (usually) has more than one implementation registered and the IHandlerSelector can "help" Windsor decide which one to use.  So:

ISubDependencyResolver - Resolves a dependency which is outside of Windsor

IHandlerSelector - Help Windsor which registered dependency to use

I wrote an article a few years ago for Visual Studio Magazine that gave examples of ISubDepedencyResolver and IHandlerSelector:

https://visualstudiomagazine.com/articles/2011/12/01/windsor-beyond-dependency-injection.aspx

---
Patrick Steele
http://weblogs.asp.net/psteele

On Tue, Dec 22, 2015 at 4:11 AM, zloidooraque <par...@gmail.com> wrote:

What is the fundamental difference between using ISubDependencyResolver and IHandlerSelector for acquiring components in customized way?

--
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 castle-project-u...@googlegroups.com.
To post to this group, send email to castle-pro...@googlegroups.com.
Visit this group at https://groups.google.com/group/castle-project-users.
For more options, visit https://groups.google.com/d/optout.