LINQ and OO

[David Veeneman]

I've been hearing a lot about LINQ in connection with Orcas, the next
release of VS.NET. Micorosoft touts LINQ as the Next Big Breakthrough, but
it looks to me like further muddying of application layering. I use an
object-oriented development approach, and I don't see how LINQ can be
integrated.

Am I missing something? Are there any good articles on using LINQ within OO
development? Or is that, like 'army intelligence', an oxymoron? Thanks

David Veeneman
Foresight Systems

 

[DeveloperX]

I've been hearing a lot about LINQ in connection with Orcas, the next
release of VS.NET. Micorosoft touts LINQ as the Next Big Breakthrough, but
it looks to me like further muddying of application layering. I use an
object-oriented development approach, and I don't see how LINQ can be
integrated.

Am I missing something? Are there any good articles on using LINQ within OO
development? Or is that, like 'army intelligence', an oxymoron? Thanks

David Veeneman
Foresight Systems

I've been prodding v3 with a long stick for a bit. There's a lot to
get your head around. Basically if you've ever had to use IEnumerable/
IEnumerator LINQ will probably offer you something.

Here's quite an interesting tutorial/primer.
http://blogs.msdn.com/ericwhite/pages/Why-Learn-Functional-Programming_3F00_.aspx

For reference here's MS's main LINQ site.
http://msdn2.microsoft.com/en-us/netframework/aa904594.aspx

 

[Christof Nordiek]

Hi,

I suppose OO development in this context is about businessobjects presisted
in databases.
If I understand id right, for this you'll still need ORM-Tools or similar.
But this will be able to use LINQ instead of their specific object query
languages.

Greetings
Christof

 

[Jon Skeet [C# MVP]]

I've been hearing a lot about LINQ in connection with Orcas, the next
release of VS.NET. Micorosoft touts LINQ as the Next Big Breakthrough, but
it looks to me like further muddying of application layering. I use an
object-oriented development approach, and I don't see how LINQ can be
integrated.

Am I missing something? Are there any good articles on using LINQ within OO
development? Or is that, like 'army intelligence', an oxymoron? Thanks

I suspect what you're missing to start with is that LINQ is far more
than just "access to a SQL database in C#". I expect that most of my
own uses of LINQ won't touch a database at all - they'll be in-memory
manipulations.

Having said that, I don't see any problem in using ORM, which is
basically what LINQ to SQL is (with lovely aspects like compile-time
validation of queries). I've used Hibernate in a couple of projects
with a *great* deal of success - indeed, it makes working with a
database but still having OO code *easier* rather than harder. The
layer boundaries can sometimes be harder to determine, but that's a
different matter from it "not being OO".