Your comment reveals vital information. When you add that AModel from your combobox to your BModel, it will have become detached from your DbContext by then. When you then add it to your model, Entity Framework will think that you have a new object.
Since you have your Ids configured as DatabaseGenerationOptions.None, it will use the primary key you provide yourself. In your case this is the PK of the detached object. Thus, when EF tries to insert this entry it will throw the above exception because an entity with that key is already in there.
There are a few ways to solve this:
- Retrieve the existing entity
This entity will be attached to your context upon retrieval, allowing you to use this. This means an extra lookup however: first to get them into the combobox and then to use the Id from the entity in the combobox to retrieve it again from the database.
Example usage:
AModel Get(AModel detachedModel)
{
using(var context = new MyContext())
{
return context.AModels.Single(x => x.ID == detachedModel.ID);
}
}
- Attach the existing model
This should just make Entity-Framework aware that the entity already exists in the database.
using(var context = new MyContext())
{
context.AModels.Attach(detachedModel);
}
Other ways to attach is by setting the state to Unchanged
context.Entry(detachedModel).State = EntityState.Unchanged;
or Modified (in case you also changed values)
context.Entry(detachedModel).State = EntityState.Modified;
与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…