4
In MVVM, the business logic is built into the Model. The ViewModel is there to bridge between the View and the Model, so it's logic only pertains to driving the display and updating the model from user interactions with the View.
I think the disconnect you are having is trying to have an anemic model work for MVVM, and it can't. By anemic model, I mean one ...
3
IMHO a pretty correct statement in the question is this:
Everybody is explaining MVC differently.
The reason behind this is that today there is not 100% consensus among software engineers what exactly counts as MVC, and what not. So as long as your program has model classes, which are unaware of the views, and view classes exclusively responsible for the ...
1
There are different ideas what MVC means and where to put code. There is in my opionion an old view that describes that your main logic should be in the Controller, and your model should be thin, merely a way to access your data.
A newer idea is that your model should contain all your business logic and should be fat. That's why this approach is called fat ...
Only top voted, non community-wiki answers of a minimum length are eligible
