In general, WPF is the way to go if you are going to be building new rich client applications.  That said, many organizations have little to no WPF experience and from a managers' perspective, there is much more risk with a WPF approach and the timelines (timescales as they say here in the UK) are certainly going to be longer.

 

Apart from all of the features WPF brings to the table, teams programming in WPF will have an increased ability to attract top talent to work on those teams.  Techies being techies generally want to work on the latest & greatest, and WinForms is past its prime.

 

I recently came across a couple of interesting bits on the WinForms and WPF debate.  Infusion is doing a lot of work with WPF and CAB, however several of our projects spun up when Prism was still in its' infancy, so it wasn't an option.  Prism appears to be coming along nicely and I hope to be able to incorporate it into our next greenfield rich client WPF client.

 

First up is Glenn Block's Prism & CAB roundup that describes the various P&P  (and non-P&P WPFCAB by Kent Boogaart).  Second is an article by a former colleauge of mine, Josh Smith, demonstrating building the same app in WPF & Winforms and comparing the approaches.  Both are good reads.

 

Syd.