I know you blogged about this about this some ago but this morning I came across so this announcement from Redgate: http://www.red-gate.com/products/dotnet-development/reflector/announcement.

In a way it wasn’t a complete shock. It was only a matter of time…

Enjoy,
Samad

I did a similiar thing using various wrappers on top of the StaticFactoryExtension. This way seems cleaner though. Two comments:

(I hope that formatting is not screwed up too badly)

1. It does not appear to support primitive types well:

[Test]

public void FactoryMethodShouldSupportResolvingPrimitiveTypes() {

var container = new UnityContainer();

container.AddNewExtension<FactoryMethodExtension>();

container.Configure<IFactoryMethodConfiguration>().RegisterFactory<byte>(c => 33);

Assert.AreEqual(33, container.Resolve<byte>());

}

2. Child containers are not handled that well, i.e. you bind to the parent container in the RegisterFactor<T> method. I’m not sure how this could be handled though bit it seems pretty important to me. I.e. the following test:

[Test]

public void FactoryMethodShouldPassCurrentlyResolvingContainerAsFactoryParameter() {

IUnityContainer containerArgument = null;

var container = new UnityContainer();

container.AddNewExtension<FactoryMethodExtension>();

container.Configure<IFactoryMethodConfiguration>().RegisterFactory<string>(delegate(IUnityContainer c) {

containerArgument = c;

return "Hello";

});

var child = container.CreateChildContainer();

string str = child.Resolve<string>();

Assert.AreEqual("Hello", str);

Assert.AreSame(child, containerArgument);

}

It’s a bit sad that it requries emitting IL to generate extensions!!

I hope you can work around these issues since I need the child container feature…

Greets, Andreas

blogs.msdn.com/…/strongly-typed-

www.thejoyofcode.com/…/Avoiding_Primit

Simon