Printable View
Hi,
I'm shifting to MVC and I noticed that LINQ is heavily promoted on books and sample apps. There's plenty of disclaimers that LINQ and MVC are not joined on the hip.
I want to ask this question because I want to keep an open mind. How many of you think that LINQ "clutter" up the language? It actually benefits me because I've been using SQL forever. However, MS could have implemented the "SQL" features through an object model.
Please feel free to expand on this thread as you see fit.
Thanks,
I don't think LINQ clutters up anything. Been using it for a while now at work, and in a lot of cases, it's cleaned up our code. It's reduced the amount of code, and in some cases, not only does it run faster, but it's now more obvious as to what the code does. Having said that, we use ourt LINQ excusivled against objects, we do not use it for retrieving data from the database or anything. Our architecture wouldn't allow for it. Also, while there are some places where we used the query syntax, the preference is towards the functional syntax.
As for the object model, that's where Entity Framework comes in. I haven't had the chance to work with it, but from what I hear, it's the next layer in objectfying databses.
-tg
Hey,
In terms of LINQ to SQL, it was my understanding that going forward, the preference would be to use the Entity Framework.
Gary