I think the answers here are missing a vital point – that this behavior is configurable out of the box via release policies – check out the documentation on the castle project site here. In many scenarios especially where your container exists for the lifetime of the hosting application, and where transient components really don’t … Read more
There are two things that you have to do to create an overriding instance: Assign it a unique name Call the IsDefault method So to get the example to work: this.WindsorContainer.Register( Component.For<IMediaPlayerProxyFactory>() .Instance(mockMediaPlayerProxyFactory) .IsDefault() .Named(“OverridingFactory”) ); Because I plan to use this overriding patten in many tests, I’ve created my own extension method: public static … Read more
I think you’re basically on the right track – If you have not already I would suggest taking a look at Rhino Igloo, an WebForms MVC framework, Here’s a good blog post on this and the source is here – Ayende (the Author of Rhino Igloo) tackles the issue of using Windsor with webforms quite … Read more
The MVC3 IDependencyResolver interface has a big problem: no release method. This means that there is a potential memory leak if you are going to use it with Windsor. See my blog post about it here: http://mikehadlow.blogspot.com/2011/02/mvc-30-idependencyresolver-interface-is.html
To answer your questions: That is using reflection and each time that an object is called from the container, reflection must used so performance will be terrible. (Is this the case? does it use reflection on every call?) No, it does not. Most of the time it uses little reflection when you register the component. … Read more
I’ve had a bit similar problem but with Unity instead of Castle Windsor. My requirements: I wanted to avoid singleton registrations on the container. All objects are resolved in Hub and should be disposed on Hub destruction. Registrations reused across Web Api and SignalR. Object lifetime is managed by HierarchicalLifetimeManager – child containers resolve and … Read more
Having recently spiked the use of 6 of these (Windsor, Unity, Spring.Net, Autofac, Ninject, StructureMap) I can offer a quick summary of each, our selection criteria and our final choice. Note: we did not look at PicoContainer.Net as one of our team considered the .Net port to be quite poor from the Java version. We … Read more
It’s called open generic, and yes, Windsor does support that. container.Register(Component .For(typeof(IAdapterFactory<,>)) .ImplementedBy(typeof(AdapterFactory<,>)) .LifestylePerWebRequest());
In general, all components in an application should be composed as late as possible, because that ensures maximum modularity, and that modules are as loosely coupled as possible. In practice, this means that you should configure the container at the root of your application. In a desktop app, that would be in the Main method … Read more
See here and here for a pretty thorough technical comparison of several IoC containers, although somewhat outdated by now (they’re from before Windsor 2.0) However, I don’t think there are really any vital features that Windsor offers and other containers don’t. Windsor, StructureMap, Spring.NET have all been around for several years and have been used … Read more