Answer Posted / 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 |
Post New Answer View All Answers