CSLA.NET 3.5 using LINQ to SQL vs. LINQ to Entities?

CSLA.NET 3.5 using LINQ to SQL vs. LINQ to Entities?

Old forum URL: forums.lhotka.net/forums/t/4847.aspx

ktran posted on Wednesday, May 14, 2008

If I am starting with the newest version of the CSLA.NET 3.5.1 framework and using a fresh normalized SQL 2008 Database, what do you reccomend using within the framework as far as going with LINQ to SQL classes or should I use LINQ to Entities classes in the DalLinq assembly?

Are there any real performance differences in using one or the other?

I created a EDM in the DalLinq project assembly and tried to use the same implemenation that is being used in the ProjectTracker.Library using the Csla.Data.DataContext and I got an error telling me that I couldn't use it for SqlEntityClient??

Does the framework support Linq to Entities?



RockfordLhotka replied on Friday, May 16, 2008

You really don't want LINQ to Entities - just the Entity Framework. You can use EF much the same way as I use L2S in ProjectTracker.

I haven't incorporated an EntityContextManager into Csla.Data yet because EF isn't released. The EF data context object isn't the same as the L2S data context, so a different manager class will be required.

If you want to use EF now you can copy the ContextManager class and modify it to work with an EF context instead - and when EF is released I'll put something along that line into CSLA.

ktran replied on Monday, May 19, 2008

Great, thanks for the input and insight on that, I'll keep inline with Linq to Sql and using the ContextManger in CSLA for now.


Copyright (c) Marimer LLC