You are quite right!
I just started with WPF about a week ago (comming from WinForms). I really like the new Frame work, but there still is a lot of work needed by Microsoft to make it WinForms equal.
One point is, that a LOT!!! of functions, that I am used to in WinForms, one very important one being menu merging, is not available in WPF. Shure, yout could code something to do that task for you, but that is in my opinion a step back towards stone age.
Also, a lot of controls, such as the simple numeric updown control is missing in WPF. As with the last point, you can code one, but this is a step back as well.
Last but not least is XAML a PITA! Even the old declarative "Language" for coding native Windows API Forms is easier. With all that and no really feasable designer at hand (no, expression blend is not that good either), it is rather hard to do more than just putting some buttons together and giving them a fresh look.
Certainly, when these points are all addressed, it would be a great framework! But to be honest, since MS didn't upgrade the designer in VS2010 very much and didn't add the missing functionalaty in .net 4, I don't know if they ever will. And if they don't, WPF is a dead framework for me. Until they make some major changes in the framework and tools that allow usability as easy and widespread as in WinForms, WPF is not a feasable solution for any programmer, that doesn't have to use the advanced features it provides.
