Using LINQ to SQL in an ASP.NET MVC2 Project

Question

Well, I'm new to this ORM business. We have to create a big project. I read about LINQ to SQL. whether it would be advisable to use it in a project with a high level of risk. I did not find any problems with him personally, but the fact is that someday he will not come back. So I need feedback from the ORM gurus here on MSDN. Will entity structure be better? (I doubt LINK for SQL because I read and heard negative feedback here and there)

I will use MVC2 as a framework. So please give feedback on LINQ to SQL in this regard.

Q2) I am also a fan of stored procedures, as they are precomputed and fixed, and I never worked without them. I know that LINQ to SQL supports stored procedures, but will it be possible to abandon the stored procedure, a beautiful data access layer created with minimal effort, since we also need fast development.

Q3) If there are some changes in some fields required in the database in LINK to SQL, how the changes will be posted at the data access level.

Answer 1

Linq-to-Sql vs Entity Framework, Entity Framework. .NET 4.0 VS2010 Microsoft soooo Entity Framework (EF) 4.0. : POCO NTier ( , , , , EF ), Lazy Loading, Sql... EF ( T4), , . , , EF 4, ( Mocks ..). -, mvc2 . q2-q3) - EF - , , . . EF, , . , EF, Linq sql:), ... , , . , , Microsoft / LinqToSql .

,

Answer 2

ok , , , .