Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I was googling for this point where why the local or global variables are not allowed as sources for WPF data binding; only the wrapping property can be bound to.
So the question is where properties are the wrapper over the variables then why these properties are allowed and the variables are not allowed.
I need to know under the hood system.
The mechanisms used for binding (PropertyDescriptor, DependencyProperties etc.) only use properties, that’s the reason you can’t bind to fields. Properties can provide validation, change notification and more, which is another reason to prefer properties. Fields provide none of these.
Also, using public fields is usually bad practice, so why should they bother implementing binding to fields? It would only promote those bad practices.