+1  A: 

If you work on a big project with (interface-)designers on the one and programmers on the other hand, WPF can be better than Forms as you can separate you GUI from your code much better through the xml.

But generally speaking I wouldn't see myself in a position to once and for all decide over WPF / Windows Forms.

Kevin D.
+1  A: 

WPF will require .NET 3.0 (or later) and will lend itself toward better seperation of your presentation / business logic / data access layers. If you have a UI Designer or you are proficent in Expression Blend WPF is probably the way to go.

If there is not a UI Designer and seperation of concerns is not an issue, WinForms will not introduce any additional learning curve to your project.

Nate Bross
Separation of concerns should *always* be an issue...
Bob King
Yes, but even with WinForms a high level of separation can be achieved, WPF just makes it easier to do the right thing ;)
Nate Bross
+2  A: 

We went to WPF and never looked back. At this point I recommend doing all new development in WPF because the experience is that much better. But take that with a grain of salt, especially if you have a team with alot of WinForms experience.

Bob King
A: 

By the looks of it, Visual Studio is going WPF as well. A New Look for Visual Studio 2010

Ralph Shillington