Linq To Sql or classic ADO.net?
Posted
by Spyros
on Stack Overflow
See other posts from Stack Overflow
or by Spyros
Published on 2010-06-15T11:56:24Z
Indexed on
2010/06/15
12:02 UTC
Read the original article
Hit count: 310
I am asking my self many times before start writting a new app or data access library , should I use LinqToSql or classic ADO.net , I have used both and the development time I spend on building an app with Linq To sql is like the 1/3 compared to ADO.net.
The only think I like using Linq to sql is that I dont have to design the domain objects Linq does that for me and saves me from spend my time on boring things :P But is Linq to sql suitable for large scale projects , is there an overhead that we can avoid when using ADO.net ?
© Stack Overflow or respective owner