RadDocking with DocumentHost shows a binding error in the VS output window
Posted on:21 Nov 2012 12:20
I also get this message.
Posted on:12 Sep 2013 15:19
Two years and still no fix? We are trying to manage our own binding errors, which is difficult when your controls are constantly throwing them.
Posted on:16 Oct 2013 13:52
The problem still exist in the latest release "2013 Q2 SP1" !!
Posted on:04 Dec 2013 05:30
The problem still exists! Please fix it!
Posted on:28 Feb 2014 14:11
It looks like this problem is very difficult to be resolved , it still exist in the latest release "Q1 2014" !!
Posted on:27 May 2014 09:31
Same problem here!
Posted on:28 May 2014 10:01
After further investigation this issue is related to a know timing issue in the WPF platform which is why the issues status is being set as "Declined". More information can be found in the official social MSDN forums here: http://social.msdn.microsoft.com/Forums/vstudio/en-US/564e7160-df70-4e95-945d-60954dd7a2ae/wpf-binding-errors-systemwindowsdata-error-4?forum=wpf
Such issues should be ignored as they are timing issues in the WPF platform itself and are not critical for runtime. If you would like not to see them in the output after building your project you could use the following workaround:
- In your project's code behind set the DataBindingSource.Switch.Level to Critical. The next code snippet shows the described workaround:
System.Diagnostics.PresentationTraceSources.DataBindingSource.Switch.Level = System.Diagnostics.SourceLevels.Critical;