Home/ Questions/Q 854301
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-15T07:54:15+00:00

I am asking my self many times before start writing a new app or

  • 0

I am asking my self many times before start writing a new app or data access library , should I use LINQ to SQL 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 don’t have to design the domain objects LINQ does that for me and saves me from spend my time on boring things 😛 But is LINQ to SQL suitable for large scale projects, is there an overhead that we can avoid when using ADO.net ?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I love LINQ to SQL; it’s easy to work with your data model. If you have .NET 4, consider using ADO.NET Entity Framework, as its the future and it supports multiple databases.

    There is a slight overhead with LINQ to SQL if you use LINQ queries against your database, but I think its negligible in most respects. We have had good performance. Additionally, it supports stored procedures, so you always have that to fall back to from a performance perspective.

    • 0