objectcontext

Does someone knows how to call a StoredProc using the same transaction of an objectContext SaveChanges method (EntityFramework 5)? The goal is to apply the objects changes and call a stored Proc that does some "magic" on the DB, but, if something goes wrong (either with the SaveChanges or with the SP execution) no changes would be committed at all. Steps: Create the context get the connection from the context Create the transaction (TransactionScope) Open the connection (will enlist the connection into the ambient transaction created in 3. and will prevent from closing the connection by the

We have a multi-layered Asp.NET Web Forms application. The data layer has a class called DataAccess which impements IDisposable and has an instance of our Entity Framework Object Context as a private field. The class has a number of public methods returning various collections of Entities and will dispose its Object Context when it is disposed. Due to a number of problems we've been facing, we decided it would be a big plus to keep the Object Context (or an instance of DataAccess ) in scope for longer on the server. A suggestion was made to keep an instance in the HttpContext.Current.Items

I've created the following Context to be used with Entity Framework Code First : public class Context : DbContext { public DbSet<Animal> Animals { get; set; } } Now I would like to use this Context in an Asp.Net application to perform CRUD operations using a GridView . I need to create a DataSource to do the data binding. How would I go about? The ASP part would look like this: <asp:GridView runat="server" DataSourceID="animalDataSource" DataKeyNames="AnimalID" AutoGenerateColumns="false"> <Columns> <asp:BoundField DataField="Description" HeaderText="Description" /> <asp:CommandField

I'm new to the Entities Framework, and am just starting to play around with it in my free time. One of the major questions I have is regarding how to handle ObjectContexts. Which is generally preferred/recommended of these: This public class DataAccess{ MyDbContext m_Context; public DataAccess(){ m_Context = new MyDbContext(); } public IEnumerable<SomeItem> GetSomeItems(){ return m_Context.SomeItems; } public void DeleteSomeItem(SomeItem item){ m_Context.DeleteObject(item); m_Context.SaveChanges(); } } Or this? public class DataAccess{ public DataAccess(){ } public IEnumerable<SomeItem>

I'm building a 4 layered ASP.Net web application. The layers are: Data Layer Entity Layer Business Layer UI Layer The entity layer has my data model classes and is built from my entity data model (edmx file) in the datalayer using T4 templates (POCO). The entity layer is referenced in all other layers. My data layer has a class called SourceKeyRepository which has a function like so: public IEnumerable<SourceKey> Get(SourceKey sk) { using (dmc = new DataModelContainer()) { var query = from SourceKey in dmc.SourceKeys select SourceKey; if (sk.sourceKey1 != null) { query = from SourceKey in

Paraphrasing from this MSDN documentation ... An INSERT statement is generated by the Entity Framework and executed on the data source when SaveChanges is called on the ObjectContext. If the INSERT operation succeeds, server-generated values are written back to the ObjectStateEntry. When AcceptChanges is called automatically at the end of the SaveChanges execution, a permanent EntityKey is computed by using the new server-generated values. This does not seem to be occurring in my code. When I call ObjectContext.SaveChanges() , an UpdateException is thrown with InnerException.Message value: