Few weeks later than originally expected but here it is – Castle Windsor 3.0 (along with its facilities and Castle.Core) achieved release candidate status. There is one major new feature in this release: registration API gained ability to specify properties to ignore/require. There are some scenarios...
The title says it all. If you can’t wait grab the binaries here (Windsor with Castle Core and facilities) and here (just Core) . Nuget package will hopefully follow soon. What’s in it? This is a major release and there’s quite a lot of new features, as well as some significant changes...
Exactly one month after release 2.5.0 we released first minor update to this release for Windsor and Castle.Core. It contains some minor improvements and fixes for issues that were identified after the 2.5 release. Complete changelog for Windsor contains 20 items, and 9 for Castle.Core, including single...
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...
I was looking at Sharp Architecture project and as I went through the codebase (the sample application in particular) I found several spots that weren’t using Windsor in a optimal way, and few other that could really benefit from some of the new improvements in version 2.5. So instead of keeping...