entity-framework-4.3

IValidatableObject.Validate only gets called when the implementing entities DbEntityEntry.State differs from "Unchanged". And just changing a navigation property won't change the state and so the validation will never occur. Why Microsoft always releases half-baked beta things? I cannot even detect the navigation property change by hand: var changes = context.ChangeTracker.Entries() .Where(e => e.State != EntityState.Unchanged) .ToArray(); Returns an empty array. There are a few interesting points here. EntityFramework tracks changes to navigation properties independently on the changes to

Trying to run down an error in my EF datacontext implementation that is yielding a fairly cryptic error. Test Name: Nodes_can_be_saved Test FullName: MyProj.Test.Integration.AFDataContextTest.Nodes_can_be_saved Test Source: c:\Users\pvencill. \Documents\Visual Studio 2012\Projects\MyProj\MyProj.Test\Integration\AFDataContextTest.cs : line 49 Test Outcome: Failed Test Duration: 0:00:01.4192808 Result Message: Test method MyProj.Test.Integration.AFDataContextTest.Nodes_can_be_saved threw exception: System.Data.Entity.Infrastructure.DbUpdateException: Error retrieving values from ObjectStateEntry

I am using the Entity Framework 4.3, POCO, database first and I am getting the following error: Internal .NET Framework Data Provider error 1025. QUESTION: I think that my query expresses my intent but I seem to be hitting this error, so I am wondering if anyone knows how I could structure my query differently to get around this error? Here is the scenario... I have a SQL server 2008 database that has 2 tables - A and B: A AId (int - not null - identity - primary key) AName (nvarchar(10) - not null) B BId (int - not null - identity - primary key) SomeName (nvarchar(10) - not null) AId (int -

I'm currently using EF Code First 4.3 with migrations enabled, but automatic migrations disabled. My question is simple, is there a data annotations equivalent of the model configuration .WillCascadeOnDelete(false) I would like to decorate my class so that the foreign key relationships do NOT trigger a cascading delete. Code sample: public class Container { public int ContainerID { get; set; } public string Name { get; set; } public virtual ICollection<Output> Outputs { get; set; } } public class Output { public int ContainerID { get; set; } public virtual Container Container { get; set; }

Could someone help me with this: The code: Role r = new Role { ID = 1, Name = "Members" }; ctx.Roles.Attach(r); //Saving User User u = new User { Login = login, Password = password, Status = 1 }; u.Roles.Add(r); ctx.Users.Add(u); ctx.SaveChanges(); What I'm trying to do is to save a new user with an existing role. User and Role classes have a many-to-many relationship mapped by fluent-api as follows: modelBuilder.Entity<User>() .HasMany(u => u.Roles) .WithMany(r => r.Users) .Map(x => { x.ToTable("USER_ROLE_XREF", dbsch); x.MapLeftKey("ID_USER"); x.MapRightKey("ID_ROLE"); }); But when the

We have the following set of objects. public class Form { public int FormId { get; set; } public DateTime DateCreatedOn { get; set; } public string Status { get; set; } } // This is using TPT inheritance from Form [Table("FormA")] public class FormA : Form { public string ExtraInfoA { get; set; } public virtual ICollection<Child> Children } // This is using TPT inheritance from Form [Table("FormB")] public class FormB : Form { public string ExtraInfoB { get; set; } public virtual ICollection<Adult> Adults } public class Person { public int PersonId { get; set; } public int FormId public