Any reason to use "Entity SQL" if you can use LINQ?

Question

Reading a book on Entity Framework and they say that LINQ is only available for C# and VB.NET. But for other languages you can use Entity SQL.

If you are doing a project in C#, is there any reason to use Entity SQL anyway? Any experiences with this?

Answer 1

It depends the "size" of your project.

On a project with very few entities, and if you're not afraid to put your linq2sql in presentation layer, it can do the trick.

Regarding Entity Framework, the lack of implicit lazy loading makes it a no go for me.

I'd go for ActiveRecord or NHibernate.

Finally, you can have a look at this post : http://stackoverflow.com/questions/252683/is-linq-to-sql-doa

Answer 2

Maybe it could be for something that can't be expressed in Linq?

Though best to rethink what you are doing though because this is usually the hint of smelly code instead as Linq is fairly complete

Some people may want to use it for dynamic filters or orderbys, but probably best to use a mix of Linq and Dynamic Linq

See

http://stackoverflow.com/questions/566984/is-there-a-way-i-can-dynamically-define-a-predicate-body-from-a-string-containing