Should I use the Model-View-ViewModel (MVVM) pattern in Silverlight projects?

Question

One challenge with Silverlight controls is that when properties are bound to code, they\'re no longer really editable in Blend. For example, if you\'ve got a ListView that\'

Answer 1

I've always thought MVVM and PresntationModel http://martinfowler.com/eaaDev/PresentationModel.html are essentially the same thing. PresentationModel is a lot easier to say. I've used it succesfully in java swing, windows forms, WPF and silverlight. If you think in terms of separation of concerns a Presentation Model makes a lot of sense. You have one class whose only concern is providing a Presentation friendly Model.It really doesn't matter what technology is used to show it on the screen. It might change some implementation details but splitting the concerns apart is a good idea no matter how you show the information. Because of that separation you can easily write tests against your presentation model regardless of the view technology. So that's a plus.