CODEWITHSUNDEEP
castle-windsor
Tao
Tao

Reputation: 51

Castle Windsor resolve named instance and unnamed instance incorrect

I have following testing code trying to get one instance for generic and other for special purpose.

[TestMethod]
public void Test_Name_And_Named_Instances()
{
//MyClass implemented IMyClass
MyClass genericInstance = new MyClass("generic");
MyClass specialInstance = new MyClass("special");

IWindsorContainer container = new WindsorContainer();
container.Register(Component.For(IMyClass).Instance(genericInstance));
container.Register(Component.For(IMyClass).Instance(specialInstance).Named("special"));

IMyClass genericOne = container.Resolve<IMyClass>();
IMyClass specialOne = container.Resolve<IMyClass>("special");

Assert.AreSame(genericOne, genericInstance); //true
Assert.AreNotSame(genericOne, specialOne); //false
}

I expect to get two different instances, but the result is both genericOne and specialOne points to same objec genericInstance.

Any idea?

Upvotes: 0

Views: 2340

Answers (1)

Mauricio Scheffer
Mauricio Scheffer

Reputation: 99730

This doesn't compile:

container.Register(Component.For(IMyClass).Instance(genericInstance));

Should be:

container.Register(Component.For<IMyClass>().Instance(genericInstance));

Other than that, the test passes for me (Windsor 2.5.2)

EDIT:

If you flip the registrations, the test fails. This is by design. When you resolve without an explicit name, you're saying "give me the default component for this service", which in Windsor is the first registered component for that service type, by default.

If you need different components under the same service type, assign explicit names to all of them when registering and resolving.

Upvotes: 1

Related Questions