Good practice for async databinding, regarding entity-framework.

Question

I have some issue to find a good pattern to keep my UI responsive using asynch databinding and entity framework which is not thread-safe. It would be a shame if the UI came to totaly freeze with no feedback for a connection lost.
So, entity framework is not thread-safe. Which mean I won't be able to rely on lazy loading here and involve than if I do async databinding to a collection of object, each object will have to load their navigations properties with their own context to display
data. Ok, I can handle this. But what if I need more than displaying data and I want to modify a navigation property ?
I need when I set the navigation property in my viewmodel to attach an entity from the same context than the parent entity is from. So here I have one context for multiple thread. What do I do ? =(
Does anyone have some experience in it and can help me to clear this mess from my mind ? =D
All the sample I can find about async databinding don't go any further than make a Thread.Sleep before returning a string, it's not realy helpfull.

Answer 1

There are reasons people post simple explanations.
One of those is because they post blog entries when they're learning something rather than when they are expert in it.  The blog post is part of their learning process.
I sometimes share context. 
What I do is put the context in Application.Current.Resources and then go get it from there when I need to re-use that particular one.
xxxDomainContext DBContext = new xxxDomainContext();
Application.Current.Resources.Add("DBContext", DBContext);
and using that:
context = (xxxxDomainContext)Application.Current.Resources["DBContext"];
You can alternatively share collections in a similar way.  Depends on how many related tables you have, but reading a whole tree of static data is sometimes a good idea rather than just one table at a time.
One technique I use is to cache slowly changing data on the client and then go get changes since the last run off the server.  For a fair few applications, yesterdays data is good enough for most data sets.  It's just the odd one or two which you really
need up to date numbers or whatever.
You can see a collection shared in this sample ( but the sharing is for different reasons ) :
 https://gallery.technet.microsoft.com/Dynamic-XAML-Composed-View-e087f3c1
Please don't forget to upvote posts which you like and mark those which answer your question.
My latest Technet article - Dynamic XAML