MVVM Series: Introduction
My head hurts just thinking about MVVM... There's quite a lot of rhetoric out there about what MVVM is and how to best implement it. And the hard part is that a lot of it is correct, even though seemingly at odds at times. To add to the confusion, I put forth my own opinion that, as with all true engineering efforts, you need to use your brain and do what works best for you, your team, and your products. This the heart of MVVM to me - MVVM is simply a pattern that can be used to make your software of a higher quality and more reusable and resilient to layer/requirement changes. Use it as best suits your needs. Forget about what you may hear or read about the 'rules' or 'laws' or MVVM - there are none. It's a pattern. Nothing more. Some people say that you should have no code-behind, ever. Some say you can. The correct information is that there are no rules about code-behind or anything else, because it is...just...a...pattern, not a programming lan