>>Is it just me, or is WPF REALLY difficult to learn?? I picked up a book and got a few chapters into it and walked away thinking "WTF????".
>
>I don't know which of the many posts in this thread to tack this onto, so I'll just use the OP.
>
>MVVM is the way to go with WPF (this coming from someone who has barely scratched the surface, but it seems to be true AFAICT). I've been reading quite a bit of Josh Smith. He's got a great way of explaining things, IMHO.
>
>Here is a quote from Josh Smith's article on Templates (found at http://joshsmithonwpf.wordpress.com/2008/06/15/understanding-templates-in-wpf/ :
>
>"The mental shift that I had to make, when leaving WinForms? and entering WPF, is that a UI is made of templates. Forget about building a UI and then shoving data into it. That’s not the WPF way. In WPF we show data in a user interface, instead of showing a user interface that contains data. It is a subtle, yet crucial, distinction. If you find yourself creating a UI in WPF and then filling it with data, you are not doing things the WPF way. If you find yourself seeing the UI as a mere "outfit" that data "wears" then you are on the right track. At least, that’s my opinion."
>
>~~Bonnie

Interestingly enough, I just received my copy of this month's CoDe Magazine. Paul Sheriff has an article on page 10 entitled "Why use WPF".