ASP.NET MVC: Should I pass primitives to my actions or should I use Model Binders?

You might also compromise and use the default model binder to bind your simple properties and get the complex properties from the value provider and fill them in "manually." For a model with only simple properties the default model binder would be sufficient. For those with one or two complex properties, those which aren't handled by the default model binder, you could still save significant amounts of code without having to write the custom model binder.

The complex binding code could be written using shared methods on a class. Once the binding code in your controller needs to cross controller boundaries or becomes significant, refactor it into your custom model binder.

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.