Common Programming mistakes for WPF developers to avoid?

Question

what are the common mistake can be avoided by a WPF developer?

Do you mean mistakes when using XAML or are thinking about WPF specifically? — Enrico Campidoglio, Jun 10 '10 at 08:25
possible duplicate of [What are the most common mistakes made in WPF development?](http://stackoverflow.com/questions/322612/what-are-the-most-common-mistakes-made-in-wpf-development) — luvieere, Jun 10 '10 at 09:03

score 4 · Answer 1 · answered Jun 10 '10 at 08:34

4

I think a big mistake would be to ignore the M-V-VM Pattern that should be used by good developers

answered Jun 10 '10 at 08:34

Mohnkuchenzentrale

5,745
4
30
41

score 3 · Accepted Answer · answered Jun 10 '10 at 08:23

3

Treating it like Windows Forms.. Don't do that.. WPF != WinForms..

answered Jun 10 '10 at 08:23

Arcturus

26,677
10
92
107

5

Sadly most of the WPF Books doesn't even write about the MVVM Pattern to use with WPF. They all write their samples like they were Winforms ... – Mohnkuchenzentrale Jun 10 '10 at 08:33

score 2 · Answer 3 · answered Jun 10 '10 at 09:16

Putting code (validation, coercion logic, change notifications, logging, etc) in the getters and setters of dependency properties' corresponding CLR properties, instead of using the PropertyChangedCallback, ValidateValueCallback and CoerceValueCallback.

Normal .NET code can get or set the property values through them, but WPF gets and sets these values by going directly to the backing store.

The CLR wrapper should thus look like this:

public int Prop
{
  get
  {
    /*NOTHING IN HERE*/

    return (int)GetValue(ThingyProperty);
  }

  set
  {
    /*NOTHING IN HERE*/

    SetValue(ThingyProperty, value);

    /*NOTHING IN HERE*/
  }
}

score 1 · Answer 4 · answered Jun 10 '10 at 08:35

1

Over-engineering... just because it is possible to do with a complex binding doesn't mean you can maintain it...

EDIT: And doing things in XAML that should be done elsewhere.

answered Jun 10 '10 at 08:35

Goblin

7,970
3
36
40

3

And doing things in Code that should be done in XAML – TalkingCode Jun 10 '10 at 09:17

score 0 · Answer 5 · edited May 23 '17 at 11:48

0

Check this out -

What are the most common mistakes made in WPF development? What are the most common mistakes made in WPF development?

edited May 23 '17 at 11:48

Community

1
1

answered Jun 10 '10 at 09:05

akjoshi

15,374
13
103
121

and this one - http://stackoverflow.com/questions/2597591/common-wpf-pitfalls – akjoshi Jun 10 '10 at 09:14

score 0 · Answer 6 · edited Sep 21 '15 at 12:12

0

Treating it like Windows Forms or ASP.NET
Ignoring the MVVM Pattern
Overusing the MVVM pattern in sake of MVVM pattern
Treating it like Silverlight
Ignoring XAML coding guidelines -> result in unmaintainable XAML.
Ignoring Binding errors in Visual Studio Output
Ignoring Designer in Visual Studio (i.e. WPF application blendability)

edited Sep 21 '15 at 12:12

PScr

449
2
11

answered Jun 10 '10 at 09:15

Anvaka

15,658
2
47
56

Common Programming mistakes for WPF developers to avoid?

6 Answers6