If I have a WPF listbox and I bind its itemssource to a list of objects. If the object members are public but don't have a { get; set; } the binding will fail. Why?
- 2Actually a getter is enough unless you want to bind both ways.brunnerh– brunnerh2011-06-02 21:36:29 +00:00Commented Jun 2, 2011 at 21:36
- Does this answer your question? Why does WPF support binding to properties of an object, but not fields?Peter Duniho– Peter Duniho2020-03-19 03:11:43 +00:00Commented Mar 19, 2020 at 3:11
Add a comment |
2 Answers
I think what you're really asking is "Why do I have to use properties instead of just fields?" And the answer is that that's just how WPF bindings work. You have to bind to properties on objects. The binding system doesn't look for matching fields.
Comments
The binding is looking specifically for Properties, not fields. That's why bindings work on PropertyPath objects.
