The policy injection block seems useful but I don't understand why it can't be put together a little differently. In my last project I ended up using CAB, Enterprise Library, and a version of the DI container that Brad Wilson posted. I started looking
at the 3.0 EL to see if the validation block might be useful.
Now I see that yet another dependency container based on Object Builder may be needed. I would like to understand why so many containers and configurations are necessary? The core of what each container provides is the same but each is configured, managed,
cached, etc. individually. It would be easier for me to understand and extend Object Builder functionality into my applications if it was centrally configured and better documented.