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...
A bit later than expected (ah, work) I published beta 2 of Windsor 2.5 today . The release has the following changes as compared to beta 1. Silverlight version (for Silverlight 3 and Silverlight 4) is now included in the package. Synchronize Facility is now included in the package (.NET only) The following...
Well it’s about time. Due to certain events (like me relocating to the other part of the world) it’s later than planned but it’s here – beta 1 of Castle Windsor 2.5 is available for download . There’s been quite a lot of changes in the release. Not just in the code but in the entire Castle Project. We...
What you’re seeing here, is a feature in very early stages of development. It’s very likely to change in the very near future, hopefully based on your feedback which I’m looking forward to. It is often the case with IoC containers, especially when registering components by convention...
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...