Click here to Skip to main content
15,121,963 members
Articles / Desktop Programming / XAML
Posted 19 Dec 2007


24 bookmarked

Debugging WPF Databinding

Rate me:
Please Sign up or sign in to vote.
4.00/5 (6 votes)
3 Jan 2008CPOL2 min read
How to debug WPF Databinding


How much do we use DataBinding in WPF? I would say a lot… I guess DataBinding is one of the biggest features of this platform. Sometimes we need to debug the values that are passed in the Binding, yet since the data binding is created by the XAML parser we do not have any way to create a Visual Studio breakpoint and step into the code…

Implementing the Solution

One way for debugging data binding is to use a converter and set a breakpoint in the Convert method. This can be cumbersome to work with since you have to create a dummy Converter and set breakpoints inside it. It would be nice if there is a way in which one can just enter a flag in the Binding and the debugger would break to let you check out the Binding values. This can be achieved by using markup extensions. Markup extensions are basically a way in which one can create instances of specific objects from XAML. For example {Binding PropertyX} is a markup extension to create a Binding object. So what we can do is basically create a markup extension that returns a Converter that we can use to debug the Binding. The converter calls the Break method of the Debugger class to force a breakpoint in the Convert method.

The markup extension for our converter would look something like this…


Basically the most important part is the ProvideValue method of the markup extension. Here we create an instance of the converter and return it. Now what we need to do is to make the Binding use this markup extension in order to use the DebugConverter (that will automatically break the debugger so that you can debug your Binding). The following XAML shows how easy it is to use the extension:

<Window x:Class="DebuggingDataBinding.Window1"
    Title="Window1" Height="300" Width ="300">
  <Grid Height="{Binding RelativeSource =
      {RelativeSource AncestorType={ x:Type Window}}, Path =Height,
      Converter={local:DebugBinding }}">

Basically the Converter={local:DebugBinding} does the whole thing. It will create an instance of the Converter and return it to the binding Converter property. So there you have it - a simple, yet handy markup extension to debug data binding.


This article, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)


About the Author

Other Uniblue Systems (
Malta Malta
Check out my Blog

Currently building a WPF Controls library aka AvalonControlsLibrary

Comments and Discussions

QuestionGreat idea Pin
t0mcat7814-Jul-11 4:18
Membert0mcat7814-Jul-11 4:18 

General General    News News    Suggestion Suggestion    Question Question    Bug Bug    Answer Answer    Joke Joke    Praise Praise    Rant Rant    Admin Admin   

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.