Home/ Questions/Q 128479
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-11T05:38:31+00:00

Problem Statement I’m writing a very basic WPF application to alter the contents of

  • 0

Problem Statement

I’m writing a very basic WPF application to alter the contents of a configuration file. The data format is an XML file with a schema. I want to use it as a learning project for MVVM, so I have duly divided the code into

  • Model: C# classes auto-generated from xsd.exe

  • View-Model: View-friendly representation of the Model.

  • View: Xaml and empty code behind

I understand how the View-Model can make View-binding a breeze. However, doesn’t that leave the View-Model <-> Model semantics very awkward? Xsd.exe generates C# classes with arrays for multiple XML elements. However, at the V-VM level you need Observable Collections.

Questions:

Does this really mean I have to keep two completely different collection types representing the same data in coherence?

What are the best practices for maintaining coherence between the Model and the View-Model?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. I’m not a big expert, but I think that is the case yes. The general idea is indeed to propagate change between the view and the viewModel via Binding, and then between the ViewModel and the Model via events (in the Model -> ViewModel direction) or dependency (in the other direction).

    I don’t know how standard that is, but my understanding of MVVM is that the ViewModel should hold a reference to the model so that when the user modifies the view, the ViewModel should call the appropriate code on the model. The other way round, the Model should raise events when modified, and the ViewModel should update itself accordingly (the ViewModel being an observer to the model).

    • 0