Starting WPF MVVM. Use a framework? [closed]

Question

I took a look at some questions here at stack overflow like this & mix10 building your own mvvm framework

I wonder if as a beginner its better to start from scratch (but I heard from the vid, its not recommended) or use a framework

also which is more suited as a beginner framework to learn? I find that after reading quite a few articles or even tutorial videos I am still quite lost. I may get parts here and there but still not there.

caliburn micro a smaller framework easy to learn? or something from microsoft like MVVM toolkit or Unity/Prism (whats the diff bet all this MS frameworks btw)? MVVM Light?

Answer 1

IMO, there no need to use a framework. MVVM is just a way of doing things.

For a start, you only need a RelayCommand class, so you can bind commands to your viewModel. You can download it from Josh Smith MVVM Foundation

Then when you are more advanced you can add other classes like:

• ObservableObject: This is intended to be the base class for ViewModel types, or any type that must provide property change notifications. It implements INotifyPropertyChanged and, in debug builds, will verify that all property names passed through the PropertyChanged event are valid properties. This class used to be called ViewModelBase.

• Messenger: The Messenger class is a lightweight way of passing messages between various ViewModel objects who do not need to be aware of each other. This is based on the Mediator implementation created by Marlon Grech and Josh Smith, as seen on Marlon's blog.