It was something I was asked after giving a presentation on Windsor, and I had not considered it before. As I've used several IOCs I wasn't sure whether this was available or not.
On Oct 27, 11:03 am, xtoff <[email protected]> wrote: > not really. Why would you want that? > > On Oct 27, 3:04 am, IanT8 <[email protected]> wrote: > > > > > > > > > Does windsor support the notion of public and private components? For > > example, if Component A depends on Component B and both are registered > > on the container, client code can directly resolve an instance of > > Component A but not Component B. Component B would essentially be > > invisible to client code, part of the inner workings of A only. -- You received this message because you are subscribed to the Google Groups "Castle Project Users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/castle-project-users?hl=en.
