Switching from Linq-To-SQL to Entity Framework for WCF Data Services Issue with FK "Properties"

Question

So, In my old Linq-To-SQL I would write code like this

var tableItem = new Table
{
    Prop1 = var1
    Prop2 = var2,
    Prop3 = var3,
    ParentTableID = parentRecordID
};

db.Table.InsertOnSubmit(tableItem);
db.SubmitChanges();

After converting my working code from Linq-To-SQL to Entity Framework (v3.5) the ParentTableID property is no longer there and I'm at a loss as to how I can create this related child record.

I'm not sure what I should change for my entity framework version, besides the obvious call to SaveChanges(); instead of SubmitChanges() :(

The solution at http://stackoverflow.com/questions/480872/entity-framework-setting-a-foreign-key-property/ has fixed my compiler errors, but I'm still working through some other stuff errors. I'll see what I find. — Nate, Jun 24 '10 at 20:47
Agree with marc_s; EF4 is much more production-ready. Upgrade if at all possible. — Stephen Cleary, Jun 24 '10 at 20:58
@marc_s, you can easily find/set the IDs through the `EntityKey` property, if you care to, in 3.5 SP1. — Craig Stuntz, Jun 25 '10 at 13:36

score 0 · Answer 1 · answered Jun 25 '10 at 13:35

For .NET 4, you can use FK associations.

For .NET 3.5 SP1 (I'm guessing at your property names; fix it if I guess wrong):

var tableItem = new Table
{
    Prop1 = var1
    Prop2 = var2,
    Prop3 = var3,
    ParentTable = db.Table.Where(t => Id == parentRecordID).First();
};

db.Table.AddObject(tableItem);
db.SaveChanges();

score 0 · Accepted Answer · edited May 23 '17 at 10:27

0

I ended up using the solution here: Entity Framework: Setting a Foreign Key Property.

edited May 23 '17 at 10:27

Community

1
1

answered Jul 01 '10 at 22:11

Nate

30,286
23
113
184

Switching from Linq-To-SQL to Entity Framework for WCF Data Services Issue with FK "Properties"

2 Answers2