Comments on: Why you should never build another website or app without LINQ

By: Donald Organ

Donald Organ — Mon, 10 Mar 2008 23:20:38 +0000

This approach has its mind in the right place how ever the amount of keystokes to get data is the same as actually typing out a query.

If you want to take a framework to the next level check out http://www.andromeda-project.org This “un-framework” allows you to put all you business rules into the database and let the database worry about, as well a create a zero code administration area for all of your data.

The andromeda database framework takes frameworks to the next level, and even includes the ability to use smarty templates to give you “Easy Reporting”

By: onur Gumus

onur Gumus — Tue, 11 Mar 2008 08:24:24 +0000

that’s not linq. That’s linq to sql. And that really isn’t very nice for me. I prefere linq to nhibernate

By: David Baxter

David Baxter — Tue, 11 Mar 2008 13:13:05 +0000

@Donald: As someone who has done both the traditional approach and now LINQ, I can tell you that the amount of keystrokes is A LOT fewer with LINQ. Its not accurate to compare just typing in the SQL queries. If you do traditional queries, then you need a framework that supports them. Takes a lot of typing to get that setup. With LINQ, you don’t need the framework cause it is already there.

I will check out the framework you mention though.

@Onur: You are right, I am describing LINQ to SQL. There is also LINQ to XML and another one that I can’t remember off the top of my head. The fact that there are more ways to use LINQ just adds to the reasons to start using it.

By: Martin Short

Martin Short — Tue, 11 Mar 2008 13:14:18 +0000

I’ve been drooling over LINQ for a while, sadly working in a Java shop where framework overload and closure discussions outshine everything else. *sigh*

By: David Baxter

David Baxter — Tue, 11 Mar 2008 13:33:52 +0000

I completely understand Martin. I worked with Java for two years just about the time .NET was coming out. It can be frustrating when you see new technology coming out and you can’t do a thing about it…

Imagine the poor souls still working with Powerbuilder

By: Charlie

Charlie — Tue, 11 Mar 2008 14:44:17 +0000

Nice article

Did you check the speed of LINQ? I have several major project to build now, and per several tests I did LINQ is slower than the traditional ADO methods.

There is no doubt that starting a project with LINQ and managing it with LINQ is much easier. The question is about speed at runtime.

10Q

By: David Baxter

David Baxter — Tue, 11 Mar 2008 14:52:52 +0000

Hey Charlie, glad you like the article. I, personally, have not done any formal speed tests, but from what I have seen, they seem about the same.

For most projects the queries aren’t gnarly enough that speed would be an issue. However, from the articles I have read, and the presentations I have seen (at last year’s TechEd), the queries that LINQ builds are supposedly highly efficient.

If speed is a major issue for part of your app (i.e. the heavy queries), then maybe a traditional route would be better for those pieces. For the more mundane stuff (i.e. adds, updates, deletes, etc), LINQ would be a huge time saver.

David

By: Bill Craun

Bill Craun — Sun, 16 Mar 2008 15:16:11 +0000

First link to the Scott Guthrie series is broken. Below is the link to the first post in the series which has pointers to the others in his series. Also, a PDF book format of the series has been created and can be downloaded from IT-Box.

The links respectively:

http://weblogs.asp.net/scottgu/archive/2007/05/19/using-linq-to-sql-part-1.aspx
http://it-box.blogturk.net/2007/10/19/linq-to-sql-tutorial-series-by-scott-guthrie-pdf-book-format/

-bill

By: David Baxter

David Baxter — Mon, 17 Mar 2008 12:09:35 +0000

Thanks for the heads up and the links Bill. I fixed the typo in my link so it should be good now.

David