LINQ to SQL

Question

I want to construct a data layer with access CRUD access to every table in 3 database about 100 tables in all. I would also want to create overloaded functions to access the data by passing in different parameters and add some business logic where needed.

Would this be a good fit for Linq to SQL or Entity Framework. I want to keep this simple but do it right. I use Linq to object and but have not used Linq to SQL or Entity Framework.

Suggestions and thoughts are appreciated.

Vulpes · Answer

You may like to check this previous thread which, to some extent, covers the same ground: http://www.c-sharpcorner.com/forums/thread/246927/is-it-true-that-linq-has-been-abolished.aspx I think there are two reasons why most of the more recent articles address the entity framework rather than LINQ to SQL: 1. When the entity framework first came out, hot on the heels of LINQ to SQL, many developers really did think t hat the latter was being deprecated in favor of the former and that impression still lingers today. 2. The entity framework is harder to understand than LINQ to SQL and so there's more meat for article writers to get their teeth into. So, if you're just using SQL Server and want to keep it simple, I'd still go for LINQ to SQL. However, if you're nervous about making the wrong choice, why don't you build trial apps using both technologies and see which you feel the most comfortable with.

Vulpes · Answer

As long as you're using SQL Server, I'd agree with Mahesh. LINQ to SQL doesn't work with any other database.

Lawrence Pond · Answer

Most of the articles I am finding on the internet are very old when it comes to Linq to SQL. This is a concern because I don;t what to get down the road and find I am on the wrong road. Microsoft appears to have abandoned Linq to Sql for Entity framework. What do you Suggest, currently the only database we support is SQL Server.

Mahesh Chand · Answer

Do you need any other features of Entity Framework? If you're good at LINQ, I would recommend LINQ to SQL.