You probably could handle this by writing your own ISubDependencyResolver implementation that would do that for you. The container alone does not allow that, and most likely it never will. Why?
The short answer is - by doing that you make assumptions about you component's dependency dependencies, which is a no-no and container is all about removing this kind of knowledge from the caller.
I starred this at work so I could answer it at home, but you beat me to it :) – Mauricio Scheffer Jan 22 '09 at 23:53.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.