Why bother with EF?
-
I've recently started a project and decided to use Entity Framework, but have come to grinding halt when it comes to updating an entity with a foreign key. After days of research, I've now discovered that EF doesn't support updating Parent-Child foreign key relationships. Using a simple example from NorthwindDB: The table Products has a foreign key to Suppliers (SupplierID). If I have a CRUD usercontrol for Products and a combobox list of Suppliers, how do you update a Product with the selected Supplier. Surely, this is a basic requirement of any application designing a CRUD application? Now, I understand that in .NET 4 this will be available. But how do I do this now! If this isn't possible, I'll have ditch EF and go back to using Datasets, which I was trying to avoid in this new project! Which asks another question, why use EF in any DB application? I'm a little desperate now :(( as my project is now 2 weeks late, so any further advice would be fantastic :confused: A little more info on my project: Server-Side: WCF Service with EF Client-Side: WPF Web Application using MVVM template