>- I know you're not a big fan of WinForms, but I agree with your views on WPF. Yes, you can build some rather cool things with WPF, but from developer efficiency I still say it's a step backwards. What is hard to understand is this: WCF came out at the same time as WPF (3.0 framework). WCF has been, IMO, a well-conceived piece of technology from day 1. WPF, by comparison, has been more convoluted.

Nah, WCF is just as convoluted. It ships with crappy default values. I understand WHY - it's meant to limit the attack surface for things like denial of service - but they basically mean the first time you write an app using WCF it will work during testing but immediately fail as soon as you put it into production. The error messages suck. The tracing app. is nice but it's kind of hidden - it needs to be much more readily accessible. Configuring via the XML file is really clumsy.

I really like the data binding model in WPF, but the XAML code is weird. There are definitely things in it that feel like they changed the standard way of doing things just for the sake of change, and I still really wish there was a nicer way of handling building re-usable controls.