WPF vs. Windows Forms

This thread is about three and a half years old but I want to add a couple of things anyway.

I am reading a book about WPF and it is saying essentially the same thing as "Easy to create an own Look and Feel" but it is not clear what that means. I hope the book (later) explains WPF well enough that I understand why WPF is considered to make that easier to do.

One thing that developers seem to overlook is that Windows Forms is built upon Windows more directly than WPF. This is both an advantage and a disadvantage. To the extent that Windows is poorly designed, Windows Forms suffers from that poor design. I also get the impression that Windows Forms was designed by VB programmers that did not understand the advantages of object-oriented programming, and to the extent that that is true, I can understand Microsoft abandoning Windows Forms.

I think that many developers get the term "supported" confused. Not supported typically means that something won't be fixed if it is broken. An absence of improvements however does not mean that something is not supported. There are many things that can be done using the Windows API that is not yet available in Windows Forms but generally speaking there is not many improvements in the UI portions of the Windows API yet the Windows API UI is still very supported. (This however might begin to change in September.)