Why you should develop systems in WPF, not WinForms
Part four of a eleven-part series of blogs

We think - cautiously - that WPF is a better platform for client tool development than Windows Forms. This blog gives 10 reasons why.

  1. 10 reasons why WPF is better than Windows Forms
  2. WPF Forms are Quicker to Create
  3. Flow Layout Trumps Absolute Positioning
  4. WPF Works for Websites (this blog)
  5. Styles are Much Better in WPF
  6. WPF is (I think) the Way of the Future
  7. Better Data Binding
  8. Selecting Controls in the Document Outline Window
  9. Triggers
  10. StoryBoards and Animations
  11. Drawing!

Posted by Andy Brown on 25 September 2012

You need a minimum screen resolution of about 700 pixels width to see our blogs. This is because they contain diagrams and tables which would not be viewable easily on a mobile phone or small laptop. Please use a larger tablet, notebook or desktop computer, or change your screen resolution settings.

3 - WPF Works for Websites

WPF is virtually the same as SilverLight (one is just a superset of the other), which means that you can publish WPF applications to a website URL:

A page in XAML

Our window created as a webpage.

 

I have to admit at this point that I've never created a web-based WPF application, although I am an ASP.NET guru.  Here's a starter for anyone wanting more information on this.

  1. 10 reasons why WPF is better than Windows Forms
  2. WPF Forms are Quicker to Create
  3. Flow Layout Trumps Absolute Positioning
  4. WPF Works for Websites (this blog)
  5. Styles are Much Better in WPF
  6. WPF is (I think) the Way of the Future
  7. Better Data Binding
  8. Selecting Controls in the Document Outline Window
  9. Triggers
  10. StoryBoards and Animations
  11. Drawing!
This blog has 0 threads Add post