The issue is that WPF and Silverlight do not allow to change the initial DataContext before the DataContext is constructed. In the case of a UserControl<>, in most of the scenarios the view model is determined based on the actual datacontext, thus
then you will indeed get the binding errors.
I have created an issue, and will think of a solution:
Probably the default listener will have to be removed and the Catel logger will now output the actual binding errors, but that is something for 2.5 (we are going to release 2.4 very soon).