Using LINQ to SQL in ASP.NET MVC2 project

Posted by mazhar on Stack Overflow See other posts from Stack Overflow or by mazhar
Published on 2010-04-24T08:12:04Z Indexed on 2010/04/24 8:33 UTC
Read the original article Hit count: 856

Filed under:
|
|

Well I am new to this ORM stuff. We have to create a large project. I read about LINQ to SQL. will it be appropriate to use it in the project of high risk. i found no problem with it personally but the thing is that there will be no going back once started.So i need some feedback from the ORM gurus here at the MSDN. Will entity framework will be better? (I am in doubt about LINK to SQL because I have read and heard negative feedback here and there)

I will be using MVC2 as the framework. So please give the feedback about LINQ to SQL in this regard.

Q2) Also I am a fan of stored procedure as they are precomputed and fasten up the thing and I have never worked without them.I know that LINQ to SQL support stored procedures but will it be feasible to give up stored procedure seeing the beautiful data access layer generated with little effort as we are also in a need of rapid development.

Q3) If some changes to some fields required in the database in LINK to SQL how will the changes be accommodated in the data access layer.

© Stack Overflow or respective owner

Related posts about LINQ

Related posts about asp.net-mvc2