Interested to Buy Any Domain ? << Click Here >> for more details...
Why do we need viewmodel in mvc?
- 1 Answers
- 10 Views
- I also Faced
- E-Mail Answers
Answer / Neha Jauhari
We need a ViewModel in MVC for several reasons: it simplifies the communication between the View and the Model by providing a simpler, more manageable interface; it allows us to encapsulate application-specific logic within the ViewModel, reducing the complexity of both the View and the Controller; and it facilitates data binding between the View and the Model.
| Is This Answer Correct ? | 0 Yes | 0 No |
What is the difference between adding routes, to a webform application and an mvc application?
What is the difference between asynchronous and synchronous actions? When would you use asynchronous actions?
What is the use of mvc?
What are the types of filters?
What is mvc flow?
What is the benefit of using mvc?
What are the features of mvc5?
What do you mean by corpus?
What is difference between mvc and mvvm?
Where is routeconfig in mvc?
What are the settings to be done for the Routing to work properly in an MVC application ?
What is afterFilter() used?
Design Patterns 
