Home/ Questions/Q 4612652
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-22T01:25:53+00:00

I know that mvvm calls for having a ViewModel class that wraps a Model

  • 0

I know that mvvm calls for having a ViewModel class that wraps a Model class, but I’m wondering why it’s a better practice to do this rather than just enhancing the Model class directly via partial classes. I get that you might want the Model to be auto-generated from an ORM, but you can still put the ViewModel stuff in another file via a partial class, and doing this avoids the considerable overhead of maintaining a ViewModel for every Model. So I guess the question is: what’s so bad about letting the Model have UI oriented code, as long as you separate it in the source code and don’t use the UI aspects of the Model inappropriately?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    The point is separation of concerns. Your ViewModel is built specifically for the needs of the UI; that means the data it contains is formatted specifically for the UI, whereas your Model is formatted directly for your persistence or domain logic.

    In your situation, changing your model necesarily requires then that a change is also done to the view model; when separated, each can vary independently which reduces unintended side effects.

    • 0