Michael Puleio is writing a series of articles on converting the CWAB in WCSF to Unity. This should be an interesting series for those of you interested in wanting the Web Client Software Factory to work with Unity.
For what it is worth, I have a Simple Web Application Block that I have mentioned on a few occasions that is the result of refactoring beating the CWAB from the clutches of ObjectBuilder and Enterprise Library:
It runs Patterns & Practices Guidance ( old picture below ) as well as several other client websites:
I have already done what Michael is attempting to do, and I can attest that by integrating Unity with the CWAB will allow Michael to remove chunks of code from the Composite Web Application Block. There is quite a bit of code in the CWAB that is essentially providing a CompositionContainer around ObjectBuilder that will be gone. A lot of helper methods on the WebClientApplication are gone. A lot of configuration code for registering types in a configuration file is gone. The craziness surrounding the complexity with managing singletons in a separate ServicesCollection, differentiating the injection of type mappings from regular types, and other places where we had to jump through hoops are gone.
Interesting enough, I also have a version of the Simple Web Application Block that runs on the ASP.NET MVC Framework for Composite ASP.NET MVC Applications. Now that we have System.Web.Abstractions that essentially wraps HttpContext and other HttpRuntime goodies, we don't need the wrappers that come as a part of the Composite Web Application Block as well. Here again is an opportunity to remove a bit of code.
With Unity and perhaps the use of System.Web.Abstractions, the Composite Web Application Block is a lot smaller and focused and IoC becomes so much easier and flexible. The refactoring is a welcome change.