title: WPF, MVVM, ICommand, and repositories
body: <p>I have a WPF application that looks something like this:</p>
  
  <p><img src="https://i.stack.imgur.com/nf2IM.png" alt="enter image description here"></p>
  
  <p>The viewmodel wraps the model and exposes any attributes relevant to the view via INotifyChanged. The view is also bound to several ICommand objects that handle certain behavior triggered by the view. I have an external ICommand who's sole purpose is to save the model to a database.</p>
  
  <p>Everything I've read indicates that neither the view or the viewmodel should have a reference to the repository. This is the reason for Command 3 which is outside of the viewmodel.</p>
  
  <p>My question is twofold. First, is this a reasonable architecture, and second, what is a good way to get the model instance over to command 3 so it can be put in the repository?</p>