Your reasoning is questionable and suspect to favoritism. Granted I'm sure almost nothing about MVVM, however, if an architecture which include MVC can mimic the actions with-out being forced to compose 50k traces of code, then whats the massive offer?
ViewModel only is made up of the Attributes, so you can claim that ViewModel can incorporate only People Houses from multiple Models that we have to Screen or use in an individual view site.
Also putting up the identical JSON back to the controller will rebuild the item to suit your needs so long as you determine the right model. Maybe all through MVC2 it had been a major downside.. but these days its a breeze and really hassle-free. You should update your remedy to reflect this.
for the reason that I feel it really is even even worse Should you have a ViewModel that contains a DTO, we should have the exact same difficulty.
The similarity in The 2 patterns is that they're equally wanting to different the logic with the Show. The commonest use/basis for This really is tests: you need to have the ability to complete from code (via a screening framework) all of the interactions that a person will invoke via the Consumer Interface.
I am a school scholar just Studying the MVC architecture, and this clarified a lot of the able functionalities that are exposed to the developer. If I could I'd place a star beside your answer.
3) I'm going to make a ViewModels folder. Inside of that folder I'll produce a view model in asp.net mvc new course ProjectViewModel.
(the traditional model) after which you can commonly a number of view models that symbolize that entity in numerous states.
This tactic works high-quality for eventualities exactly where the HTML UI we want to generate in just our view template corresponds fairly carefully to our domain model objects.
"Because MVC has actually been released I've observed A great deal confusion regarding how greatest to construct view models. Occasionally this confusion is not without having great purpose due to the fact there isn't going to seem to be a ton of data in existence on most effective apply tips.
The key intent of the View Model is to encapsulate all the data that the view must render, making it easier to pass this data in the controller for the view. It acts as an middleman concerning the controller and the view, encapsulating the info exhibited or edited over the view.
community class Tackle community string Identify get; established; general public string Avenue get; established; general public string Town get; established; community string Point out get; established; community string PostalCode get; established;
ViewModels tends to make the appliance safer when you don't have to reveal the possibly perilous Qualities like UserRole, isAdmin while in the ViewModel
My desire would be to make View Models unique for particular Views. While this could entail more coding - plus some might say a duplication of properties across entities and View Models, AutoMapper helps to minimise the additional function concerned.