Question

In the msdn documentation there is a recommendation to not bind controls directly to an object query:

We recommend that you not bind controls directly to an ObjectQuery.
Instead, bind controls to the result of the Execute method.

I’ve also read some answers here on SO that recommend it and also not to bind to instance of the model itself. Nevertheless I couldn’t find why it is not recommended since all of the tests I have done so far seem to work fine.

Could anyone shed some light on the reasons why I shouldn’t use these objects for my bindings?

Answer 1

For the question “why shouldn’t I bind controls to the ObjectQuery”:

Quoted from here:

To ensure that the data source is up to date, you may need to execute
the query again using the Execute method. This will bind the control
to a new ObjectResult.

If you do not call Execute, what’s displayed in your UI might be not up-to-date compared to what the query actually returns after being executed. The binding is, of course, not automatically updated when a change occurs in the database.

Second point:

We recommend that you not bind controls directly to an ObjectQuery.
Instead, bind controls to the result of the Execute method. Binding in
this manner prevents a query from being executed multiple times during
binding.