I'm trying to connect "Office like automation object model" (like in this example: http://msdn.microsoft.com/library/default.asp url=/library/en-us/dndotnet/html/automationmodel.asp) with WPF. The problem is, that some collection are updating in it's own thread (not UI thread).

Automation Object Model + WPF
DouglasR
I was just trying to build some application using this article. That's why this name "Office like".
Let take this example: There is two Assemblies. First is Logic, second is UI. Logic does'n have any reference to WinFX assemblies. Now let's open a file. This takes some time, so I start a new Thread for this operation. While opening a file I fill some collection with items. This collection is databound to some UI Control. I get situation that collection is updating in other thread than Main.
rotninou
This is similar to your previous question about updating collections x-thread. You can build your collection to support a locking mechanism and then wrap them in a UI-layer collection that understands both lock and dispatcher.
I'm hoping to have a sample of this very soon. Watch my blog.
Michael Kenney
You said "Office like" so I assume you mean there is some other in-house/third-party model that you're working with Then you're saying the model is being updated from threads other the main thread... is that correct
Who controls the threads that are updating the model Is it part of your application or are you saying the model itself has built in threading that causes updates to happen Hopefully it's not the latter 'cause that would just be bad design and you'd be pretty much stuck. If it's the former then you just need to make sure that you always marshal updates of the model back to the UI thread. There are probably some tricks you can do even if the model is self-updating, but I'd need a lot more info to even make a suggestion as to where to start and you're going to end up writing a lot of code (shim collections, etc.) to deal with this.
Later,
Drew