castle-windsor

Is it considered bad form to register components in Windsor without specifying an interface? i.e. container.Register(Component.For<MyClass>().LifeStyle.Transient); as opposed to... container.Register(Component.For<IMyClass>().ImplementedBy<MyClass>().LifeStyle.Transient); I understand the benefits of coding to an interface rather than a concrete implementation however we are finding that we now have lots of interfaces many of them are on classes that realistically will only ever have one implementation. Mark Seemann Yes, it would be okay to register components without their interfaces, but not

in asp.net-mvc I have the Windsor Controller Factory that injects all the dependencies into the controllers, but how do you get this in Windows Forms ? for example if have this Form1, how am I going to get an instance of Form1, should I use resolve (which is called ServiceLocator and anti-pattern by some ppl)? public class Form1 { private IBarService _barService; public Form1(IBarService barService) { _barService = barService; } } Yes, in program.cs you should make windsor resolve Form1 . For the sake of being able to view the form in the designer you add an empty constructor and decorate it

I am using Castle Windsor to manage controller instances (among other things). My controller factory looks like this: public class WindsorControllerFactory : DefaultControllerFactory { private WindsorContainer _container; public WindsorControllerFactory() { _container = new WindsorContainer(new XmlInterpreter()); var controllerTypes = from t in Assembly.GetExecutingAssembly().GetTypes() where typeof(Controller).IsAssignableFrom(t) select t; foreach (Type t in controllerTypes) { _container.AddComponentLifeStyle(t.FullName, t, LifestyleType.Transient); } } protected override IController

My current understanding of Castle Windsor registration is that one can only validate registration by calling Resolve on a root component. But since windsor's component model knows each component's dependencies, it should be possible to test that all dependencies can be satisfied without actually instantiating anything. The main reason for wanting to do this is to have a unit test for registration that doesn't require me to stub components that call external resources on start-up. For example. I have a class Root that has a dependency on IChild: public class Root : IRoot { private IChild child

I have some SignalR hubs which may need to access some transient and singleton dependencies. Hooking the creation of the Hub is easy and works just fine however SignalR does its own Dispose() call on the created Hub rather than notifying the dependency resolver and letting it get involved in the disposal. This isn't such a big deal if the dependencies are registered singletons, but if they're registered as transients then they'll never get disposed (if that was required) and Windsor will keep them alive until the Windsor container is collected (when the web server is shutting down anyway). I

I have read often that Service Locators in IOC are an anti-pattern . Last year we introduced IOC (Ninject specifically) to our application at work. The app is legacy, it's very big and it's fragmented. There are lots of ways a class, or a chain of classes can get created. Some are created by the web framework (which is custom), some are created by nHibernate. Lots are just scattered around in weird places. How would we handle the different scenarios and not come up with something thats not at least ServiceLocatorish and not end up with different kernels in different places (scopes like

I'm a long-time Windows developer, having cut my teeth on win32 and early COM. I've been working with .Net since 2001, so I'm pretty fluent in C# and the CLR. I'd never heard of Castle Windsor until I started participating in Stack Overflow. I've read the Castle Windsor "Getting Started" guide, but it's not clicking. Teach this old dog new tricks, and tell me why I should be integrating Castle Windsor into my enterprise apps. Matt Hinze Castle Windsor is an inversion of control tool. There are others like it. It can give you objects with pre-built and pre-wired dependencies right in there. An