I'm elbow deep in redoing the Unity config schema right now, and part of the implementation is getting me wrapped around a pole. For those who've looked at the implementation, there's an object in there called a TypeResolver. This object is responsible for
looking at type aliases and substituting the real types for the alias. This object needs to be passed down through the config element hierarchy, and it's a real pain, with code in essentially every config property getter to set it all the way down the graph.
I have an alternative approach which is a lot cleaner, but the current configuration api:
gets in the way. Would you be extremely annoyed if I broke the API in 2.0, and instead made you do this:
section.ConfigureContainer(unityContainer) // when using default container in configuration
I am also thinking of adding an extension method on IUnityContainer to do configuration regardless:
Anyway, how painful would this public API breakage be for you? Out of the question, annoying, no problem? Thanks,