castle-windsor

I have a decorator and actual implementation that looks like this: public interface IAmUsedTwice { void DoSomething(); } public class ForReal: IAmUsedTwice { public SomethingElse Need { get; set; } public ForReal(SomethingElse iNeed) { Need = iNeed; } public void DoSomething() { Console.WriteLine("Realing doing something here"); } } public class SomethingElse {} public class DecoratingIsFun: IAmUsedTwice { private IAmUsedTwice Actual { get; set; } public DecoratingIsFun(IAmUsedTwice actual) { Actual = actual; } public void DoSomething() { Console.WriteLine("This is a decorator!"); Actual

I've been playing around with Castle Windsor lately and realized I could use it to back a container-like object I currently use already. So far I've only read information about an application having only one container instance per application. Is it correct to have many containers per application if those containers belong to different tiers? The reason I ask is because I'd like to take advantage of Windsor's dependency resolution and XML configuration for my own container-like object. I currently use Windsor integration with MonoRail and it didn't seem correct to mix in components that have

I have a MixIn that requires some state to operate. I am registering it as so.. container.Register(Component.For(Of ICat) _ .ImplementedBy(Of Cat) _ .LifeStyle.Transient _ .Proxy.MixIns(New MyMixin())) When I call container.Resolve(of ICat), I get back a proxy for ICat, which also implements IMixin. However, if I call container.Resolve(of ICat) again, I get a new proxy for ICat, but MyMixin is the SAME instance. (Which makes sense because I didn't tell the container any way to create IMixin) So, IMixin is a Singleton, even though the Component's lifestyle is Transient. How can I tell Windsor,

I have a WCF service setup with Castle.Windsor; messages arrive to a dispatcher that send them to the right component (basically a IHandler<Message> with message being a query). However in some cases there is one additional before the handler can act; the message must be completed with data coming from someplace else. What i want is to check whether there exists an injector for the type of my message and if one exists, run it. IInjector<Message> Injector = InjectorFactory.RetrieveInjector<Message>(); if (Injector != null) { Logger.InfoFormat("IInjector<{0}> OK", input.GetType().Name); Injector

There seems to be an issue with passing generic arguments when attempting to create a parametrized instance with Castle Windsor Demo of Failure to Pass Generic Arguments private static void Main(string[] args) { PassGenericParamAtResolutionTime(); Console.ReadLine(); } private static void PassGenericParamAtResolutionTime() { Console.WriteLine("Passing generic argument fails"); var container = new WindsorContainer(); container.Register(Component.For<ISandCoordinator<Simpleton>>() .ImplementedBy<SandCoordinator<Simpleton>>()); var runtimeConstructorParam = new GenericManager<Simpleton>( "This Id

I want to perform this CODE equivlant in the castle xml config file. // Foo(string name) IFoo f = new Foo(StaticBarClass.Name); XML Now for the XML, I know everything (e.g. the blah) except for the stuff inside the parameter part. What would the parameter part look like? <component id="blah" service="blah" type="blah"> <parameters> <name>StaticBarClas.Name_THAT_I_NEED_HELP_WITH</name> </parameters> One approach you could use is to replace the configuration parameters inspector with your own variant that can introduce some additional behaviour - here's a quick prototype: public class

I'm new to Castle Windsor and am just using the latest version. I've created entries for my repositories which are working fine but I have one final dependency that I'm passing into my controller. I've created a ModelStateWrapper which inherits from IValidationDictionary. The ModelStateWrapper takes a ModelStateDictionary in it's constructor so that in my code I can pass the following as an example: IMembershipService _memSvc; IValidationDictionary _validationService; public AccountController() { _validationService = new ModelStateWrapper(this.ModelState); _memSvc = new MembershipService(

A Castle Windsor question: Is it possible to register a class that has an internal constructor with the container? Thanks Joni Krzysztof Kozmic Yes, it is possible. Default component activator looks only for public constructors. You can either provide custom component activator for that component that would take internal constructor into account, or use for example factory to activate the component: var container = new WindsorContainer() .AddFacility<FactorySupportFacility>() .Register( Component.For<Foo>() .UsingFactoryMethod( () => new Foo() ) ); var foo = container.Resolve<Foo>(); However