-
Notifications
You must be signed in to change notification settings - Fork 458
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Are Child Containers still relevant? Is there any docs? #115
Comments
Child containers aren't really documented because it is recommended to use handler selectors and sub dependency resolvers in preference to child containers. There are still edge cases that don't work as people expect with child containers. Krzysztof wrote a blog series a few years back:
Most of the Windsor docs were written during the time when there were some big defects with child containers so I suspect that is why no docs were written at that time. |
Lifecycles are incredibly hard to propagate between parent child containers. This is an example of where I tried to submit a PR fixing transient disposals with parent registrations via child container resolution: #324. The question I have is why is this abstraction necessary? The Microkernel has so many ways of solving these problems(handler selectors and sub resolvers), what problem are you trying to solve by doing this? Will add this to the V5 Windsor discussion which was looking more about obsolescence but now feels like we need to delete something that should have never existed. |
Please join us over there to voice your thoughts. |
Looks like they are alive, but I have no luck trying to find anything about their behavior.
The text was updated successfully, but these errors were encountered: