Why do we need viewmodel in mvc?
- 1 Answers
- 89 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 razor syntax?
Mention what is the importance of nonactionattribute?
What is mvc routearea?
What is tempdata in mvc?
What is the use of spring mvc?
What is get and post actions types?
What are the filter in mvc?
Is mvc stateless?
What are the 3 things that are needed to specify a route?
What is data annotation in mvc?
What is the difference between "actionresult" and "viewresult" ?
What is view engine in mvc?
Design Patterns 
