Sven Groot said:
Minh said:
*snip*

I'm not sure if this is the case in Silverlight, but in regular .Net the Async pattern (unlike the Begin/EndInvoke pattern) makes sure that the Completed event is raised on the UI thread. So using UI methods from the DownloadStoriesCompleted event handler is safe since it's already on the correct thread.

This uses the AsyncOperation class introduced in .Net 2.0, it's also what BackgroundWorker uses internally.

This uses the AsyncOperation class introduced in .Net 2.0, it's also what BackgroundWorker uses internally.

Oh, really? I did not know that.

That must be what's happening in Silverlight too then