>>>>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".
>
>I got mine too. Looks like it has lots of other good articles to.
>
>For those who do not subscribe, the articles in the Nov/Dec 2009 issue are:
>
>Why Use WPF?
>Asp.Net 4.0
>VB 10
>What's new in C# 4.0
>Asp.Net MVC 2 In Action
>Silverlight 3 Highlights
>What's New in Entity Framework 4, Part 2
>
>
>This is a great magazine that everyone using or moving into .Net should subscribe to.
>
>Also, they have the "CodeCast" podcast that I listen to every episode. Hosts are Ken Levy, Gary Short, and Markus Egger.


In his artilcle on page 10, Paul Sherriff states at the top that "Microsoft now considers Winforms a legacy technology and they won't update it within Visual Studio".

Huh?? Not update Winforms?? Is this true? or is this just his opinion?

There are thousands upon thousands of winforms apps out there. I can't see how MS could pull the plug.