Home/ Questions/Q 6605733
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-25T19:19:10+00:00

We’re working with OData on Silverlight, using DataServiceCollection to get the data. All calls

  • 0

We’re working with OData on Silverlight, using DataServiceCollection to get the data.

All calls for fetching data (LoadAsync() LoadNextPartialSetAsync()) are done on a worker thread. However, the ‘LoadCompleted’ callback as well as deserialization and object materialization are done the UI thread.

We decompiled the System.Data.Services.Client.DLL where the DataServiceCollection is, and saw that indeed all code handling the response of the OData is dispatched to the UI thread.

Is there any way to get the deserialization to be called on a worker thread instead?

thanks
Yaron

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Well…

    It seems the OData collections deliberately moves processing the UI thread. I’m guessing this is done because old objects might have properties the UI is bound to. These properties might change when loading additional data.

    Using the query itself, I was able to get the response on a worker thread. However, doing this means one MUST detach the objects from the OData context (or clone them) if UI is bound to any property. Otherwise consequent queries might cause property changed events when objects are materializing on the worker thread.

    • 0