I’m not sure if it is any better or even relevant, but you might want to check out accumulating collections - http://code.google.com/p/autofac/issues/detail?id=2&can=1 - this feature might apply to your task example. Instead of ITaskRegistrar you’d do something like:

builder.RegisterCollection<ITask>()
.As<IEnumerable<ITask>>()
.Named(”tasks”);
builder.Register<ProcessApprovedRegistrations>()
.MemberOf(”tasks”);
builder.Register<RetrieveQueuedResults>()
.MemberOf(”tasks”);

The advantage might be that you can avoid an ‘early’ resolve, and I’ve already done my best to support scope in line with the other container features. You can use MemberOf(typeof(IEnumerable<ITask>)) rather than a name if that is preferable.

This isn’t a particularly well-tested feature of the container but one that I think will prove important as it is more easily maintained and extended in applications than a ‘ResolveAll<ITask>’ kind of feature. Hope this is is useful!

Nick