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 am having a data binding problem (a separate question), and normally when I code, I can use the debugger to step through, and hit break points. What is probably a simple issue has taken me all day, with no resolution (getting very frustrated now), because I do not know how to “run the debugger” on my XAML data bindings.
If anyone could explain how to do this, it would be greatly appreciated.
I have no idea if VS provides an easy way to debug bindings, but I usually use Snoop for debugging bindings
It’s a tool that will go through a WPF application and give you a TreeView of the application’s Visual Tree. You can select an element to view its DataContext and other properties. If there are any binding errors, the property is usually highlighted and it will say what the error was. If the binding is failing because the property doesn’t exist, I can usually trace the DataContext and figure out where I went wrong in my binding.