Tracking XAML based binding expression errors is an hurdle
I can think of several things I would try to do:
1. Stop whenever an exception is thrown by the expressions engine (currently only showing on the VS output window).
2. Allow you to jump to the XAML line where the expression is failing.
3. Opt in for you the default diagnostics mechanism of the Binding expression (I think it's WPF only).
4. Insert a converter that automatically let you see the value that is going over the wire and let you stop and debug (via automatic breakpoint).
Customer support service by UserEcho