No you should not use View Model if you are using information only from Model. It is a simple situation. Create strongly-typed View and use your Model directly.
eu-ge-ne
2009-06-08 17:59:26
+5
A:
Even in terms of extensibility? Because it would be much easier to add another field to a VM in case I ever need it.
Alex
2009-06-08 18:13:16
I dont think that it will be much easier to add new field to VM than create VM. In both cases you shoud plan your modification and then create test for it. In general I think that in every situation the simplest solution is the best solution.
eu-ge-ne
2009-06-08 18:19:58
+1
A:
I tend to use a domain model until I need a view model. Why? Using the domain model is faster up front. Then, when the domain model no longer covers my need, I refactor, adding what I need where I need it. I'm a big fan of "get it working quickly and refactor vigorously".
This also goes for splitting models into multiple user controls.
Jarrett Meyer
2009-06-08 18:26:47