• Learning Prism (Composite Application Guidance for WPF & Silverlight) MVVM Fundamentals

    Published by on November 16th, 2009 9:55 am under Composite Application Guidance for WPF & SL, MVVM, p&p, Patterns & Practices, Prism-v2, Prism-v2.1, Silverlight, Silverlight 3, Windows Presentation Foundation, WPF

    8 Comments

    On a previous post in this series I talked about a possible approach to take when starting to learn Prism as a whole (the Tip numbering is resumed from the previous post). In this post I will get more specific and talk about one of the most used (if not the most used) pattern when developing Prism applications (either for WPF & Silverlight): MVVM.

    Most people are familiar with this pattern (if you are not great places to read about it are here for WPF and over here for Silverlight), so I will not go deep into what is the main idea of it. Instead I will try to go over some core concepts that usually lead to different levels of confusion.

    What’s the difference between MVVM and PresentationModel?

    The above question is one asked a lot, as people tend to get confused when they hear all the talk about MVVM and then open some Prism Quickstarts or RI and find most of them “implement the PresentationModel pattern”.

    Well, there is not a certain answer (and if there was I probably wouldn’t be the one who came up with it), but as far as Prism development is concerned they are synonyms. There is no difference between them, except for the coined term. As Martin Fowler explains in his PresentationModel article: “The essence of a Presentation Model is of a fully self-contained class that represents all the data and behavior of the UI window, but without any of the controls used to render that UI on the screen. A view then simply projects the state of the presentation model onto the glass.”, so if you think about it, the way to “project the state of the PresentationModel (or ViewModel) onto the glass is WPF/Silverlight DataBinding in our case (or as Julian likes to explain it: “the ViewModel is a bindable Presenter”).

    Always remember the main objective, testability and decoupling.

    Tip 5: MVVM and Presentation Model are synonyms.

    How do I do pure MVVM?

    This is another point of confusion as people tend to relate MVVM with DataTemplates and no View code behind, so they get the idea that the only way to implement the pattern is that one.

    In my opinion there is no pure MVVM, it is a design pattern, so it can have many different implementations which will depend mainly on who implements it and what his requirements are. In this particular topic I would like to “branch you” to Glenn’s post “The spirit of MVVM (ViewModel), it’s not a code counting exercise.” as I agree with his point of view in this topic, so there is no point in duplicating the information.

    Now that you have finished reading Glenn’s post, I hope you understand what I am trying to explain (not necessarily agree). I for once like the “View First” (you “talk” to the view) implementation to relate the View to its ViewModel in Prism could be the following (using DI):

    public class MyView
    {
    public MyView(IMyViewModel viewModel)
    {
    this.DataContext = viewModel;
    InitializeComponent();
    }
    }

    In the code above, Unity’s DI provides the decoupling between the View and the ViewModel, so the ViewModel “does not have to know anything about the view” and allows you to test the VM in isolation (of course this is just one of the ways to do it).

    Tip 6: There is no Silver Bullet MVVM implementation. Use the one that you like best.

    How should I manage my View/ViewModel?

    This question addresses both creation/destruction of View and ViewModels as well as its interaction with other components in the application. Often it is not “clear” which component should handle a specific action.

    Say that when a button is clicked an event should be published. Where should this be done? Well, without information about the application and its patterns it is hard to say. It could be done in the ViewModel or it could be done in a module level controller that manages interaction with other modules, but this depends on how your application is structured.

    Instead of expanding on this topic, I would like to branch you (yet again), to these posts from Ward Bell which talk about these common questions and provide some really interesting and thought answers:

    Should I always use commands to communicate with the ViewModel?

    Before using a command, I usually stop and think: “Can this be done in another way?, Can I achieve this same functionality with binding?”. Well, sometimes the answer is yes, and that is when I think commands are not necessary. The most common example is binding a command to execute every time and item in a Listbox is selected. This same behavior can be achieved by binding the SelectedItem property of the Listbox to your ViewModel (most of the times), and executing the required action on the setter.

    Having thought of the above, what if I do need a command? Well, my first recommendation would be understanding how do Commands with attached Behaviors work, a topic explained by Julian in this great post. After that you can use the code snippet I created some time ago to help you with the tedious task of creating the classes required for this to work.

    Tip 7: Before using commands, think if there is another option.

    Things to add to your reading list

    To help you comply with Tip 4, you can find below a couple of articles about MVVM and MVVM with Prism that I think might be of use to better understand this topic (the ones mentioned above would be in this list, but there is not need in duplicating them):

    Hopefully, this post has helped you understand a little more about MVVM and how to use it with Prism. As always, your feedback is appreciated, so if you believe any link should be added or anything of the sort, just drop a comment.

    Shout it

    kick it on DotNetKicks.com

    Tags: , , , , , , , ,

    • http://www.downcastsystems.com Dave Haynes

      I’m really interested in your thoughts on how to do dialogs properly using MVVM and Prism. Most of the time the answer is “Use a mediator” or “Use EventAggregator” — how exactly? If I have a command that needs to open a new window, how should that work? I’d like to see a working example vs. a theoretical implementation.

    • Arun Nair

      Hi,
      Great information on using MVVM with Prism. I was wondering if you could post a sample where the views are hosted in a Tab Region (unlike the the examples with prism where the view itself is a TabControl.
      I am looking for an IE style tab control, which has a close button on top.

      Thanks
      Arun

    • http://blog.raffaeu.com raffaeu

      Subscribed to your RSS, your blog is pretty interesting.
      Thanks

Archives

Categories