WPF/MVVM Quick Start Tutorial over at CodeProject:
So to address this, I’ve written this based on what I would have liked to have found as the #1 hit on Google after typing ‘WPF Tutorial’. This article may not be 100% correct, or even do things ‘the one true way’, but it will illustrate the main points that I wish I had found in one place 6 months ago.
Fairly good walkthrough of MVVM and why you would use it. (I had to ramp up yesterday, and spent probably too long trying to sort out the “why”.)
- I very much appreciated that the business objects were chosen so that “Name” would not be one of the business properties. MVVM adds enough new classes, where there are enough opportunities to misunderstand and poorly name things, that having these things completely separate is helpful.
- The code is very elided. I missed the bold warning to download the code, and things were much smoother once I did. (Generally, web articles shouldn’t require that you download code samples, though.)
- I like the idea of “write something quickly, in a naive way, then patch it up with best practices.” More articles should be written from this perspective.
- However, it could be clearer when we’re doing something “quick and dirty” with the intention to clean it up later.
- I wasn’t famliar with the “xmlns:local” namespace concept, so I spent a half-hour trying to figure that out.
- I really liked the progression from not working, to working, to using a little more of the .NET framework, to growing our own framework. It made a lot of sense.
- I still have a sense that MVVM frameworks replace a lot of brittle syntax (which, to me, is unfamiliar and disorienting) with a more stable, extensible platform (which, being new to me, is also unfamiliar and disorienting).
I think good next steps from this article are to find a framework that I can try out a little more deeply. Or, I may revisit knockout.js: with a better understanding of the problems it’s trying to solve, I may have better luck with it.