If that's how you're doing WPF in VS2010, you're not doing it right.

You can't really directly compare Winforms to WPF. They are different animals. They work differently. You create them differently.

I won't reply back to you on this topic because you continually refuse to open your mind to differnent possibilities. You want to do things the way you always have. That's not how WPF works. The technology is entirely different from Winforms and requires a different methodology. I suggest you go back and read the first post in this thread, where Kevin had the same view you do until he learned to do things the right way. And whether you like WPF or not, it's the way .Net development is going and Winforms is not.

>Your still not going to code a WPF form ( or at least I havent been able to) without going into the XAML file. Once you get there you have a whole markup mata data language to deal with. limited IDE support. All to do the same job that I'd do in a winform without it.
>That takes time. Thats more code. thatsmore to debug. And in a line of business application thats not acceptable. If its going to take longer and be harder to debug then thier has to be a some benefit.