We provide all kind of trainings
corporate, online , classroom and video based trainings - www.justcompile.com www.sukesh-Marla.com
Trainer, Author, Newspaper publisher, Programmer.
I find it is always beneficial to put my domain objects (business object, database objects etc.) into their own project. That way they are stand alone and independent of any program that uses them.
Doing things this way the Model in MVC is always the View Model.
We provide all kind of trainings
corporate, online , classroom and video based trainings - www.justcompile.com www.sukesh-Marla.com
Trainer, Author, Newspaper publisher, Programmer.
I agree with you. As far as I understand View Model is another concept used in MVVM pattern. In this article ViewModel is still model. When we create a new project using Asp.Net MVC template in Visual Studio. We see ViewModel classes like LoginViewModel and ForgotViewModel. I understand this is still model classes. They are using this to make clear the differences between domain entities and model. They call domain entities -> model and model -> viewmodels. It's just the way we name our model classes, but we are still using the same pattern (MVC). Let me know if it makes any sense.
We provide all kind of trainings
corporate, online , classroom and video based trainings - www.justcompile.com www.sukesh-Marla.com
Trainer, Author, Newspaper publisher, Programmer.