datacontext

The context objects generated by Entity Framework are not thread-safe. What if I use two separate entity contexts, one for each thread (and call SaveChanges() on each) - will this be thread-safe? // this method is called from several threads concurrently public void IncrementProperty() { var context = new MyEntities(); context.SomeObject.SomeIntProperty++; context.SaveChanges(); } I believe entity framework context implements some sort of 'counter' variable which keeps track of whether the current values in the context are fresh or not. With the code above - called from separate threads - do I

I have several methods that deal with DB and all of them start by calling FaierDbDataContext db = new FaierDbDataContext(); Since the Linq2Sql DataContext object implements IDisposable, should this be used with "using"? using (FaierDbDataContext db = new FaierDbDataContext()) { // use db here } What are the implications of using it one way or another? Sadegh Unlike most types which implement IDisposable, DataContext doesn't really need disposing - at least not in most cases. I asked Matt Warren about this design decision, and here was his response: There are a few reasons we implemented

Here's the issue: I have 2 data contexts that I would like to do a join on. Now I know that LINQ doesn't allow joins from one context to another, and I know that 2 possible solutions would be to either create a single datacontext or to have 2 seperate queries (which is what I'm doing for now). However what I would like to do is to "simulate" a join. Here's what I've tried. using (var _baseDataContext = Instance) { var query = from a in _baseDataContext.Account.ACCOUNTs where a.STR_ACCOUNT_NUMBER.ToString() == accountID join app in _baseDataContext.Account.APPLICATIONs on a.GUID_ACCOUNT_ID

I have a Page page in a Frame frame , with frame.DataContext = "foo" . (page.Parent as Frame).DataContext is "foo" . ok BindingExpression for page.DataContext is null (also forced with ClearValue). ok page.DataContext is null . but I expected "foo"! Why isn't the DataContext inherited? As far as I understand the Frame sandboxes the content. But I couldn't find any documentation of this behavior - can anyone point me to a place where this is mentioned? To answer your question about documentation of this behavior: It's not Microsoft documentation, but I have a couple of WPF books that both

I am having some trouble figuring out how to set the correct DataContext on a ContextMenu . I have a collection of view models who are the source of an ItemsControl . Each view model has a collection of items which are also the source of another ItemsControl . Each item is used to draw image which has a ContextMenu . The MenuItems in that ContextMenu need to bind to a command on the view model, but the PlacementTarget of the ContextMenu is pointing to the individual item. My Xaml looks something like this: <ItemsControl ItemsSource="{Binding Markers"}> <ItemsControl.ItemTemplate> <DataTemplate