This is what I ultimately did, but it was pretty laborious, and I'd still like to find a better solution.
The model was found to be overly polluted by determining whether an entity was previously associated or already existed in the database (implementing...IEquatable<T>...
is OK, however I believe incorporating...IEntityWithKey...
On my POCOs, the...
Apply the...AsNoTracking()...
How to stop entities from being cached: (...here...)...var set = _dbContext
.Set<T>()
.AsNoTracking()
.ToList();
this.AddRange(set);
This is true, of course. ...This article outlines numerous techniques for attaching and adding entities.... gives the following example:...var existingBlog = new Blog { BlogId = 1, Name = "ADO.NET Blog" };
using (var context = new BloggingContext())
{
// The next step implicitly attaches the entity
context.Entry(existingBlog).State = Entity...
From page 80 of the DbContext book by Lerman & Miller:...Calling ...DbSet.Add... and setting the ...State... to ...Added... both achieve exactly the same thing....That is:...If the entity is not tracked by the context, it will start being tracked by the context in
the ...Added... state. Both ...DbSet.Add... and setting the ...State... to ...Added...
No other way to achieve it except to modify EF.
I believe that few folks using EF 6 accomplished this with a text backing field and some restrictions (Bar and Bar children does not access to EF persisted property or you need other work after deserialization).
