I have been reading several articles and books on the Mvvm pattern for WPF programming. The articles and books are fairly consistent with the conepts/content. But I have also been working with several Wpf/mvvm sample projects, and they all seem to work differently. Some projects are straight forward Model/View/ViewModel folders in the sample project. But I have a couple of sample projects that use the MvvmLight toolkit and the SimpleMvvmWpf toolkit. These toolkit projects contain additional content that I have not seen in the books or articles. Well, I'm starting to see a little bit of conent in the articles about Services folder, Locator folder, but it is making it quite difficult for me to see the fundamental mvvm pattern.
I have been working with one sample mvvm project that could be the breakthrough for me. And here is where I need a little help. The project is called TheWorldsEasiestMvvm. The author wrote all the code in the code behind of mainwindow.xaml. He explains that this is obviously not loosely coupled but for demonstration purposes, and I can kind of follow the pattern. A copy of this sample project is located here sample project
What I want to do is to rewrite this project using the Modle/ViewModel/View folders. So I need to split out the code. Here is where I am having the problems. The first question is this --
1) for this particular (very simple) project do I just create a standard WPF project and manually add my own Model/ViewModel/View folders? Or do I want to use some toolkit?
2nd question) How do I split out this sample code? Sometimes it seems that I have seen the DelegateCommand (RelayCommand...) code located in a .cs file in the root folder or sometimes in the ViewModel folder.
My request is for an explanation how to split out the code in this sample mvvm project to make it follow looslely couple mvvm
paradigm.
Thank you
Rich P
