May 2, 2012 at 8:13 AM
Edited May 2, 2012 at 8:15 AM
The framework is well designed. however something look strange about IoC dependency injection.
I just look at the EmailClient sample and found the ApplicationController "ask for" container (in constructor) and parse it into another controller.
this class has a dependency on container.
public CreateEmailAccountController(CompositionContainer container, //...)
So you need to create a CompositionContainer for UnitTest?
Why not ask for things that really needed. (just IMO, there is no "best" or the "only" right way to design.)
public CreateEmailAccountController(EmailAccountsViewModel emailAccountViewModel, CreateEmailAccountViewModel createEmailAccountViewModel, //...
* I 've heard some discussion about parsing the whole container from GoogleTechTalks -
The Clean Code Talks