WPF looks complicated compared to WinForms---why?

  • Thread starter Thread starter raylopez99
  • Start date Start date
R

raylopez99

Took a look at a demo of font dialog for WPF, and it looks
complicated. You could do the same thing in C# 3 WinForms 2.0 in about
one-half to one-fourth the code.

So I wonder, for you that have made the transition to WPF, how much of
the seemingly extra code in WPF is due to code separation and how much
is for the new 'transparent' Aero/Vista type interface, and how much
for other stuff (security, accessibility, localization, etc)?

Curious before I make the leap (which I plan to). But WinForms is
very easy IMO--after about two months I feel pretty confident, though
things do blow up daily and I struggle to fix them (with a little help
from my friends).

RL

Accessibility - Accessibility Best Practices

Security - Windows Presentation Foundation Security

Localization - WPF Globalization and Localization Overview
 
raylopez99 said:
Took a look at a demo of font dialog for WPF, and it looks
complicated. You could do the same thing in C# 3 WinForms 2.0 in about
one-half to one-fourth the code.
Click to expand...

Without looking at the specific code for both examples you're
referring to, it's hard to tell. For that matter, do you count the
XAML markup for code? Because if you do, you should really count the
generated *.designer.cs files for WinForms as well...
 
Back
Top