Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Sorry to tell you but this feature <strong>DOES NOT</strong> exist in WPF XAML nor does it exist in WinRT XAML. I can't find an official source for WPF, but here is a pretty official one for WinRT (<a href="http://social.msdn.microsoft.com/Forums/en-US/toolsforwinapps/thread/fae53937-cb47-45da-b740-49f75f8d36e9/" rel="noreferrer">http://social.msdn.microsoft.com/Forums/en-US/toolsforwinapps/thread/fae53937-cb47-45da-b740-49f75f8d36e9/</a>) he insinuates pretty strongly that this was an effort spearheaded purely by the Silverlight team and can possibly be expected in future versions of WPF and WinRT. </p> <p>So far the best debugging techniques I've seen are as follows:</p> <p><strong>1) WinRT &amp; WPF: Output Window</strong> Using the output window with the proper options enabled, make sure Tools->Options->Debugging->Output Window->Data Binding = "Warning" or something else useful...</p> <p><img src="https://i.stack.imgur.com/hDE6O.png" alt="enter image description here"></p> <p><strong>2) WinRT &amp; WPF: Use a converter</strong> Using a converter and just setting a break point inside the converter. Or you can build/use something similar to how WinRT XAML Toolkit does: <a href="http://winrtxamltoolkit.codeplex.com/SourceControl/changeset/view/9c814f6c67c540adbd6952821a351d9ffa4d1d99#WinRTXamlToolkit.Debugging/Converters/BindingDebugConverter.cs" rel="noreferrer">http://winrtxamltoolkit.codeplex.com/.../WinRTXamlToolkit.Debugging/Converters/BindingDebugConverter.cs</a></p> <p><strong>3) WinRT: Use <code>DebugSettings.BindingFailed</code></strong></p> <pre><code>App.Current.DebugSettings.IsBindingTracingEnabled = true; App.Current.DebugSettings.BindingFailed += (s, e) =&gt; { // debug the failed binding here }; </code></pre> <p>see: <a href="http://msdn.microsoft.com/en-us/library/windows/apps/windows.ui.xaml.debugsettings.bindingfailed" rel="noreferrer">http://msdn.microsoft.com/en-us/library/windows/apps/windows.ui.xaml.debugsettings.bindingfailed</a> for more information</p> <p><strong>4) WPF: Use <code>PresentationTraceSources.TraceLevel</code> Attached Property</strong> Gives you a verbose output of the binding, see: <a href="http://msdn.microsoft.com/en-us/library/system.diagnostics.presentationtracesources.tracelevel.aspx" rel="noreferrer">http://msdn.microsoft.com/en-us/library/system.diagnostics.presentationtracesources.tracelevel.aspx</a> for more information.</p> <p>I realize this is an older question, but I couldn't find a good source of information for everything XAML, found this answer off a search engine and noticed it was still lacking an answer. It doesn't help that there are technically 3 versions of XAML going by the same moniker. So here's the dump of everything I found while investigating debugging bindings. Enjoy, hope it helps someone... -ck</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    3. VO
      singulars
      1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload