Why do we need viewmodel in mvc?
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 are the filters?
What does Model, View and Controller represent in an MVC application?
Is react an mvc?
Is angular mvvm or mvc?
What is lazy loading in mvc?
What is mvc in detail?
Explain what is routing? What are the three segments for routing is important?
Mention what is the importance of nonactionattribute?
What is the purpose of viewmodel in mvc?
Is razor pages replacing mvc?
What is the use of mockmvc?
What is meant by mvc?