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?
My $0.02 :
I’ve started using WPF / the Mvvm-pattern a few weeks ago and one route I can definitely recommend is first starting a test-project, reading a lot about mvvm, and trying to implement it yourself (even if it’s just by using parts of other people’s stuff).
Implement something, read some more, go back and change stuff, and then read some more.
Do this for the first 2 weeks and you’ll get an idea of what it’s actually all about, you’ll see some problems and find some solutions, etcetera.
Basicly this will get the mvvm-idea in your fingers and give you some hands-on experience.
Then if you like you can throw away your test-project, decide wether or not to really start writing your own stuff or using an existing kit, and probably have more appreciation and understanding for the way existing kits work.
I ended up not using an existing kit but my own very simple implementation since I didn’t need much complexity for my project, but I did get a lot more appreciation for some implementations I’ve seen discussed on the interwebs.
Edit:
When I talk about “two weeks” I mean “two weeks of sparetime” which is about 25 real hours 😉