Threading advice needed... (MVVM)

[Anders]

Hi Telerik,

We have the latest WPF library - as the project is progressing we have identified elements that we'd like to 'wrap' in busy indicator display.

When just adding the control, we are confronted with the need for code to be executed in background worker thread.

When code had been modified to be executed through the background worker, our code fails as the background thread modifies an ObservableCollection that a control relies on. .Net advices the use of Dispatcher.

However, if using the Dispatcher, I should 'go through' the control and ask it to modify the underlying collection - and that sort of violates the whole idea of MVVM.

I'm sure there's some brilliance hidden for me somewhere :) - can you enlighten me as to the recommended way of using BusyIndicator with MVVM?

Thanks,

Anders, Denmark.

[Konstantina]

Hi Anders,

I can suggest you to use a Task class, for example:

Task.Factory.StartNew(() => {
IsBusy = true;
Thread.Sleep(1000);
 IsBusy = false;
}

You can find some more information in these help resources:

• http://msdn.microsoft.com/en-us/library/system.threading.tasks.task.aspx
• http://www.eggheadcafe.com/tutorials/aspnet/21013a52-fe11-4af8-bf8b-50cfd1a51577/task-parallelism-in-c-40-with-systemthreadingtasks.aspx

Hope this helps.

All the best,
Konstantina
the Telerik team