Why you should develop systems in WPF, not WinForms
Part eight of a -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
  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 (this blog)
  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.

7 - Selecting Controls in the Document Outline Window

WPF makes it easier to select controls:

Window in WPF Window in Document Outline view
Our sample window ... ... in Document Outline view

You can select any control within the overall hierarchy, and even see what it looks like:

Document outline showing appearance of control

Impressive  programming!  You can hover over any control to see what it looks like in isolation.


It's this concept that any control (together with its children and their descendants) can be viewed as a standalone entity which makes so many things easier to do in WPF.

This blog has 0 threads Add post