Share via

More on MVC and M-V-VM

  • Article

There have been a raft of interesting articles and discussions of MVC patterns and WPF.  A practical introduction is here:

https://www.codeproject.com/KB/WPF/MVCtoUnitTestinWPF.aspx

I love the article, but must add I have always struggled with RoutedCommands and CommandBindings.  I think the APIs are too complex for what they do, but more importantly I prefer to route commands through my application model, not through WPF's element tree.  The Blend architecture contains a creature called CommandManager which makes sure commands get to their destination, and we tend to Databind directly to properties of type ICommand (I love ICommand, just not its implementation in RoutedCommand).

Meanwhile, Dr. WPF aptly summarizes the controversy:  https://www.drwpf.com/blog/Home/tabid/36/EntryID/27/Default.aspx

Basically, I have found everyone agrees you should separate your Model and your View, but the details of the rest depend on technology and personal preference.

Comments

  • Anonymous
    February 06, 2008
    PingBack from http://www.biosensorab.org/2008/02/06/more-on-mvc-and-m-v-vm/

  • Anonymous
    February 07, 2008
    The comment has been removed

  • Anonymous
    February 14, 2008
    Interesting discussion without reading the controversy. There has always been a longing for that perfect MVP windows / web architecture and It feels like we are all almost here. "The Taligent Programming Model" by Mike Potel still holds truth. Looking forward to this next push in architecture from Microsoft.Net. Has anyone else conceived of a code generation architecture strictly confined to the PresenstationCore? Rob