Well urm, its not much help, but i found a quote on wiki:
Quote: "The Windows Presentation Foundation provides a platform-independent way of designing graphical user interfaces. Windows Forms has been in effect superseded by WPF (and its associated GUI declarative language called XAML). Since WPF is relatively new, it is unclear if Windows Forms will continue to be improved in future .NET releases."
Quote: "WPF vs. Windows Forms
WPF
+ Powerfull styling and skinning structure
+ Easy to create an own Look and Feel
+ Does support Windows Forms
+ The future technology for developing Vista Applications
+ The ability to reuse existing code
+ Highly advanced databinding possible
- Declarative vs procedural code
- Requires .NET Framework 3.0
- Compared to Windows Forms, still in development fase
- Requires Dx9 compatible vidcard for advanced graphics
Windows Forms:
+ Extensive documentation to be found on the internet
+ Plenty of examples
+ Does support WPF
- How long will this be supported? (I've read somewhere that Microsoft is only developing WPF now, only maintanance for Winforms)
- Design your own look and feel in a application is a lot of work."
Source:
http://social.msdn.microsoft.com/Forums/en/wpf/thread/42636e55-a1e0-4b29-bbd1-cd8073585584
Im pretty sure only windows can use .net framework 3.0 (but those emulators like Wine might make it work on linux)
Quote: "1. WPF is a graphical subsystem that renders user interfaces in Windows based applications; Windows Forms is the graphical API that provides access to native Microsoft Windows interface elements.
2. WPF is a markup language alternative that defines UI elements and relationships with other UI elements; Windows Forms is an event driven application supported by the Microsoft .NET Framework."
Source:
http://www.differencebetween.net/technology/difference-between-wpf-and-windows-forms/
Quote: "We took the plunge and built our latest desktop e-commerce package entirely in WPF (except for reporting, which we interop to use ReportViewer). I haven't had one day of regret. WPF's declarative approach has been easy to grasp for everyone, and it helps enforce separation of UI from business logic.
That said, if your team has a lot of WinForms experience, then it might be counter-productive to spend time learning WPF.
If that's not an issue, give WPF a try and maybe you'll get hooked."
Source:
http://stackoverflow.com/questions/504014/wpf-winforms-or-something-else/504053#504053
Hope that helped.