castle-windsor

I know it's possible to use DependancyResolver and register Castle Windsor with MVC but due to the issues described in https://stackoverflow.com/a/4889222/139392 we have stuck to the WindsorControllerFactory method of implementation on our MVC projects. However it looks like the ApiControllers are using some other kind of factory as Castle Windsor is unable to inject the dependencies. Has anyone figured out how to use Castle Windsor with ASP.NET Web API and MVC without using the DependencyResolver? Thanks to Critiano's post and some searching on-line I managed to get it to work here's the code

As the subject says, really! What do they do? Forwarded types allow you to have more than one service implemented by a single implementation, for a concrete example say we have two interfaces for working with tree nodes of some sort: public interface INodeAlterationProvider { ... } public interface IChildNodeListProvider { ... } And various components take a dependency on one or both of those interfaces. However in implementing each of those interfaces you discover that their is a lot of shared functionality and want to merge the implementations into a single class along with some other

I use the Entity Framework database-first approach to generate a DbContext / POCO model for an MVC application. I want to avoid having dependencies on DbContext in my controllers to enable me to switch to another persistence provider as I need to (for example for unit testing purposes). To do this I want to use the Castle Windsor IoC container. I plan to register DbContext as an IUnitOfWork service and to register a generic IRepository service, implementations of which I will use to access and work with aggregate roots in the model. I'm new to Windsor and haven't been able to find much info

Why would you use Castle Windsor factory auto implementation feature: AsFactory() rather then asking for needed interface? Example: container.Register(Component.For<IEmailSender>().ImplementedBy<SmtpEmailSender>()); container.Register(Component.For<IEmailSenderFactory>().AsFactory().LifeStyle.Transient); ... using (var factory = context.GetServiceFactory<IEmailSenderFactory>()) { var emailSender = factory.CreateEmailSender(); emailSender.Send(message); } Why wouldn't you simply write: var emailSender = context.GetServiceFactory<IEmailSender>(); emailSender.Send(message); Effect is the same.

I use Castle Windsor as my IoC container . I have an application that has a structure similar to the following: MyApp.Services.dll IEmployeeService IContractHoursService ... MyApp.ServicesImpl.dll EmployeeService : MyApp.Services.IEmployeeService ContractHoursService : MyApp.Services.IContractHoursService ... I use the XML configuration at the moment, and every time I add a new IService/Service pair, I have to add a new component to the XML configuration file. I want to switch all this over to the fluent registration API but haven't worked out exactly the right recipe to do what I want yet.