Link Details

Woulda, coulda, shoulda! Login and vote now.
Link 73031 thumbnail
User 111696 avatar

By bloid
via rapidapplicationdevelopment.blogspot.com
Published: Mar 30 2008 / 13:27

In my last post I described how the Where() function works for LINQ to Objects via extension methods and the yield statement. That was interesting. But where things get crazy is how the other LINQ technologies, like LINQ to SQL use extension methods. In particular it’s their use of a new C# 3 feature called expression trees that makes them extremely powerful. And it’s an advantage that more traditional technologies like NHibernate will never touch until they branch out from being a simple port of a Java technology. In this post I’ll explain the inherent advantage conferred on LINQ technologies by expression trees and attempt to describe how the magic works.
  • 11
  • 1
  • 1497
  • 518

Comments

Add your comment
User 209827 avatar

evarlast replied ago:

0 votes Vote down Vote up Reply

11 up votes??? read the comments to the blog post. Dotspot is RIGHT ON. This has ZERO to do with NHibernate. Anyone who has used NHibernate Query Generator can tell you all about strongly typed queries to NHibrernate. AND it works on .NET 2.0 and C# 2.0.

LINQ to SQL ultimately just generates a string to send to SQL Server. That isn't strongly typed! The exact same abstractions which LINQ to SQL builds can and are build on NHibernate.

Voted down for cluelessness.

Add your comment


Html tags not supported. Reply is editable for 5 minutes. Use [code lang="java|ruby|sql|css|xml"][/code] to post code snippets.

Voters For This Link (11)



Voters Against This Link (1)