castle-windsor

I have a project where my business layer is constructed using DI, but I'm trying to go an additional step and use Windsor to manage object construction. Let's just say I have a pre-existing data layer (that I don't want to modify), that can be accessed via the following interface: interface IDataFactory { IDataService Service { get; } } A series of classes in my business layer depend on the services exposed through IDataFactory: IFactory factory = DataFactory.NewFactory(); IBusinessService service = new ConcreteBusinessService(factory.Service); I understand that in order to register

I'm using NServiceBus (3.2.2), RavenDB (1.2.2017-Unstable) and Windsor (3.0.0.4001) in an MVC 4 project. I have a IHandleMessages class that handles 3 different messages, and that needs an IDocumentSession, and therefore defines a property such as: public IDocumentSession DocumentSession { get; set; } I've copied the RavenDbUnitOfWork implementation from NServiceBus' website I've registered IDocumentStore, IDocumentSession and IManageUnitsOfWork in my Windsor container as follow: container.Register( Component .For<IManageUnitsOfWork>() .ImplementedBy<RavenUnitOfWork>() .LifestyleTransient() );

do any other .NET IoC containers provide equivalent functionality to the typed factory facility in Castle Windsor? e.g. if I am using an abstract factory pattern in a WPF application: public class MyViewModel { private IAnotherViewModelFactory factory; public void ShowAnotherViewModel() { viewController.ShowView(factory.GetAnotherViewModel()); } } I don't want to have to create a manual implementation of IAnotherViewModelFactory for every type of ViewModel I wish to show, I want the container to take care of this for me. AutoFac has a feature called Delegate Factories , but as far as I can

Here is the example: interface IComponentA {}; class ComponentA : IComponentA { }; interface IComponentB { }; class ComponentB : IComponentB { }; interface IComponentC { }; class ComponentC : IComponentC { public ComponentC(IComponentA a) { Console.WriteLine("Constructor A"); } public ComponentC(IComponentB b) { Console.WriteLine("Constructor B"); } }; All these components are registered in Castle Windsor container. But class ComponentC has 2 overloaded constructors. Any of them can be used when ComponentC is being activated. I need ComponentC(IComponentB b) constructor to be used. For a

Say I have a component like this public class MyComponent { public MyComponent(string name) { } } I basically want to have the provided constructor parameters behave as part of the component identifier when resolving it. If you've never resolved it with that set of parameters, it will instantiate a new one. In other words, I want to somehow modify the following test to succeed: IWindsorContainer container = new WindsorContainer(); container.Register(Component.For<MyComponent>()); MyComponent a1 = container.Resolve<MyComponent>(new { name = "a" }); MyComponent a2 = container.Resolve<MyComponent