Home » MS OfficeRSS

feedback/suggestion: improve vague binding errors at run-time please

This may have been addressed already but it's so annoying, I want to make sure...
When I bind to a property that doesn't exist,

Ex: <TextBlock Text={Binding Title} /> //"Title" doesn't actually exist

I get the following run-time message for each property:

Debugging resource strings are unavailable. Often the key and arguments provide sufficient information to diagnose the problem. See http://go.microsoft.com/fwlink/?linkid=106663&Version=3.0.40806.0&File=System.Windows.dll&Key=BindingExpression_SourceConnectionFailure 
[BindingExpression_SourceConnectionFailure]
Arguments:

The problem is that it doesn't tell me anything at all about the attempted binding property so I have to guess!

Classic Silverlight applications do not have this problem.
 

2 Answers Found

 

Answer 1

Thanks for this feedback, Kevin,

I'm sending an inquiry to the Tools team regarding this, so it is on their "radar".

- Mark

 

Answer 2

I've been running into this as well.
 
 
 

<< Previous      Next >>


Microsoft   |   Windows   |   Visual Studio   |   Follow us on Twitter