-
This is a follow up to my previous post . If you haven’t yet – go and read that one first. I’ll wait. So where were we? Aha… In the last post I said, that Windsor (any container in general) creates objects for you, hence it owns them, ergo its responsibility is to properly end their lifetime when they...
-
Probably the single most misunderstood feature of Castle Windsor is regarding its lifetime management of components. Hopefully in this post (and the next one) I’ll be able to clear all the misconceptions. Why is Windsor tracking components in the first place? One of the core responsibilities of a container...
-
Continuing the topic from the previous posts. What would happen? Current behavior of Windsor is somewhat flawed. What it will do is it will resolve foo , and provide it with bar . The flaw of this behavior is that now when we resolve foo via any of the tree containers we’ll get the same instance...
-
This is a follow up to my previous post . I deliberately didn’t discuss the issues that arise when using container hierarchies to get some feedback on usage first. So what’s the problem? Consider trivial scenario: We have two components, where foo depends on bar . The dependency is optional...