How do YOU use the Entity Framework with CSLA?

Gravy posted on Wednesday, January 07, 2009

Hi guys,

Just wondering how different people envisage using the Entity Framework with CSLA.

All our database design so far uses StoredProcs for all data access so there is already have a degree of seperation between database schema and code. My initial thought on the EF when used in CSLA is that it only seems to provide a convenient way access the database. For example, create some sort of database context to your model and then access the Entity using methods and properties in code. Where as now, I use the DAAB so I have to get a connection, create a command, add the parameters then execute it.

Does anyone have a more insightful opinion or idea on how the EF could be used?

Regards

Graham

AndrewBurns replied on Wednesday, January 07, 2009

Gravy,

I am currently battling EF as the DAL on a very small project.  Just as I get one issue resolved another pops up.  The reason I chose EF as the DAL is because the LINQ queries are nice and tidy and easy to maintain.  However if I do not resolve my current issue it is back to ADO.NET for me.

Currently I am getting an EntryPointNotFoundException when I am attempting to find the EF backing item on a Child_DeleteSelf call.  Infuriating!!!

My next from scratch project I think will be NHibernate DAL with some sort of custom query passing  unless they have LINQ support up and running by that time.

sergeyb replied on Wednesday, January 07, 2009