To define the schema of an existing database, I'm using Code First. The key names in the tables don't fully align, which is my issue. With one-to-many relationships, this works well because I can utilize the...HasForeignKey()...
approach, but there doesn't appear to be a comparable concept for one-on-one interactions. My definitions for a table are...
The following is what I'm aiming to do:...public class class1
{
public int Id {get;set;}
[ForeignKey("Class2")]
public int Class2Id {get;set;}
public virtual Class2 Class2 {get;set;}
}
public class class2
{
public int Id { get; set;}
[Required]
public virtual int Class1Id {get;set;}
[Required]
[ForeignKey("Class...
This kind of activity isn't really supported by Entity Framework. Simply trying to replace an object with another object won't "remove" it from the database. Even with Cascade Delete, Entity Framework still requires that you give a delete command in order to avoid having an orphaned object in your context. Zzz-5-Zzz will override the...SaveChanges(...
