1

When I hit g (to debug) and I close a view to get to main view, I get these messages in WinDbg:

System.Windows.Data Error: BindingExpression path error: 'TileTitle' property not found on '' 'System.String' (HashCode=757602046). BindingExpression: Path='TileTitle' DataItem='' (HashCode=757602046); target element is 'System.Windows.Controls.TextBlock' (Name=''); target property is 'Text' (type 'System.String')..

System.Windows.Data Error: BindingExpression path error: 'TileTapCommand' property not found on '' 'System.String' (HashCode=757602046). BindingExpression: Path='TileTapCommand' DataItem='' (HashCode=757602046); target element is 'System.Windows.Controls.Button' (Name=''); target property is 'Command' (type 'System.Windows.Input.ICommand')..

How can I solve these? Are these really a problem? Does it cause a memory leak?

Thomas Weller
  • 55,411
  • 20
  • 125
  • 222
user2526236
  • 1,538
  • 2
  • 15
  • 29
  • 1
    Those are data binding errors in your WPF application; they are not from WinDbg. See [this answer](http://stackoverflow.com/a/16174389/1698557) for help debugging them. – Patrick Quirk Jun 11 '15 at 15:41
  • @PatrickQuirk I have reviewed that article before. I just want to know , if this might cause any memory leak. I dont see any message in output when in my VS2013. When I run the debug (g in WinDbg) I got this. my application works, run fine. – user2526236 Jun 11 '15 at 15:47

1 Answers1

1

The messages you see are not exceptions, they are debug output. You should see the same using DebugView (SysInternals), it is not WinDbg specific.

In case of an unhandled exception, WinDbg would stop and you could analyze it. In case of a first chance exception that got caught, no output would be generated (unless implemented by the developer).

As pointed out by Patrick already, see WPF Error 40 BindingExpression path error on how to read the output and find the place to fix it.

If you can't notice any failure while using the program, you might not need the binding at all and you can just remove it. However, someone put it there, surely for some reason - find out who it was (the answer is given by your version control system) and ask him why he implemented the binding. Maybe you find an undocumented requirement and then you see the failure that is caused by the missing binding.

Since the missing binding is something that is not there, this does not cause a memory leak.

Community
  • 1
  • 1
Thomas Weller
  • 55,411
  • 20
  • 125
  • 222