-
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...
-
As promised , I released Nuget packages for beta 1 of Windsor 3. This is my first major rollout of Nuget packages, so please report any issues working with them. Nuget and beta packages Nuget is quickly evolving and getting more useful with each release. However one feature it’s missing right now...
-
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...
-
As we're nearing the release date of Castle Windsor 3.0 (codename Wawel) I will be blogging about some of the new features and improvements introduced in the new version. In the previous post I introduced one new diagnostic, and in this post we’ll explore other improvements in this area. Overview...
-
As we're nearing the release date of Castle Windsor 3.0 (codename Wawel) I will be blogging about some of the new features and improvements introduced in the new version. One of the features that were introduced in current version 2.5 was support for debugger diagnostic views in Windsor. In Wawel...
-
Today we released second bugfix release for Windsor 2.5 and for Core 2.5 (incl. DynamicProxy, which is what probably is the most interesting to people). This time there are no new features, only fixes to issues identified since the last release (you can see the entire list in changes.txt). We have however...
-
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...
-
Exactly one month after beta 2, I’m happy to announce that Windsor, as well as Castle Core (which now includes DynamicProxy and Dictionary Adapter) 2.5 are officially released. Single .zip contains the following versions: .NET 3.5 (sp1) .NET 4.0 .NET 4.0 Client Profile Silverlight 3 Silverlight...
-
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...