BLOGS BY TOPIC▼
BLOGS BY AUTHOR▼
BLOGS BY YEAR▼
We think - cautiously - that WPF is a better platform for client tool development than Windows Forms. This blog gives 10 reasons why.
- 10 reasons why WPF is better than Windows Forms
- WPF Forms are Quicker to Create
- Flow Layout Trumps Absolute Positioning
- WPF Works for Websites (this blog)
- Styles are Much Better in WPF
- WPF is (I think) the Way of the Future
- Better Data Binding
- Selecting Controls in the Document Outline Window
- Triggers
- StoryBoards and Animations
- 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:
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.
- 10 reasons why WPF is better than Windows Forms
- WPF Forms are Quicker to Create
- Flow Layout Trumps Absolute Positioning
- WPF Works for Websites (this blog)
- Styles are Much Better in WPF
- WPF is (I think) the Way of the Future
- Better Data Binding
- Selecting Controls in the Document Outline Window
- Triggers
- StoryBoards and Animations
- Drawing!