Is Model only Entity Data Model class of my database? Model as simple place where i have my data? Or I can input in Model something more?
+2
A:
The model in MVVM is supposed to be the place for data-centric logic and the data, yes. It can be just the Entity Data Model, or you can add some more logic--that's up to you. The primary point is to seperate any presentation-specific logic from the model and put that in the viewmodel.
Hope that's clear enough
Sheeo
2010-03-16 02:53:15
About data-centric logic You just mean the methods which is automate created by Visual Studio when we create EDM? Or something more logic?
netmajor
2010-03-16 02:59:02
I don't think in your case you'll need to put any more in there, nope.Just stick with generated models by EDM -- and use those directly from the ViewModel
Sheeo
2010-03-16 03:15:58
+1
A:
You can do whatever you like...
Typically, though, the "model" in MVVM is considered to be an "external" class (e.g. a generated class from LINQ-to-Entities, say) and so it usually doesn't have much logic.
Dean Harding
2010-03-16 02:55:00
+1
A:
The model is the core domain logic you are dealing with. It is everything not directly related to a UI view.
An easy way to think of it is the View and ViewModel combined represent what would be a "typical" UI layer without good separation. In MVVM, you split the logical aspects (the ViewModel) from the display logic (the View).
kyoryu
2010-03-16 02:56:00