When you use a {Binding XXX} to specify a content or as a DataSource a BindingExpression path error is reported in the projects Output window.

This can be avoided by using [FieldName] rather than the {Binding FieldName} but you cannot do this for a DataSource.

When producing loger reports you get multiple binding errors for each row which take a lot of time to produce before the report is visible.

Is there a way of specifying the DataSource without getting these Binding Errors?

Thanks again for your help.

The current problem we are facing is that bindings established when the DataContext is still not set do not work later, when the DataContext is set. Assigning a special object as a DataContext seems to resolve this issue, but causes all bindings to give the error in question because they refer to properties which do not exist. A temporary solution for turning these errors off is the following: go to the Options dialog in Visual Studio (Tools -> Options menu). In the dialog select Debugging -> Output Window and set Data Binding to Off.

Regards,
Meppy