There is a new hype about Linq to SQL now. And honestly, I don't get it. May be I am too old :)
Anyway, I would not care about this much if it was just about how you write your code. The problem is that to save few lines of code you loose performance. I wanted to compare how much is lost when I found that someone already did it here.
Friday, January 02, 2009
Linq to SQL performance
Subscribe to:
Post Comments (Atom)
2 comments:
Also, MS says Linq to SQL is going to be phased out by ADO.net entity framework. Probably yet more slower ;) How's CSLA perf comparing to pure ADO.Net?
CSLA does not cover data access itself. We use ADO.NET to retrieve and update data (SqlDataReader, SqlCommand), the latest sample that comes with CSLA written with Linq to SQL.
I was in our local .NET conference and saw demo on Alexandria. That's where they are going really.
Post a Comment