Just Curious

[Jorgen Andersson]

You mean rolling your own and posting an article about it? :)

Wrong is evil and must be defeated. - Jeff Ello

[RickZeeland]

Quote:

A nod's as good as a wink to a blind bat.

:-\

[Jacquers]

I used to... but not anymore.

[DJ van Wyk]

Daily, yes. You just have to be very careful with how you write the queries and constantly inspect what Linq-to-SQL projects into actual SQL. Sometimes Linq is so clever that it project terrible and slow queries but in most cases you can fix it by "rewording" your Linq queries. I believe Entity Framework has the same projection problem.

My plan is to live forever ... so far so good

[decaffeinatedMonkey]

Entity Framework Core for me. I like how it does migrations, and if done right, it can be portable across multiple database engines.

[darktrick544]

Never have, I dont mind writing proper code

[Mario Luis]

Nope. MS did suggest a while ago that it should not be used production wise, rather use EF or some such.

[obermd]

Nope. Since I write mainly in VB I find the Linq syntax to be very cumbersome and hard to use. When I write in C# I'm far more likely to use Linq simply because the lambda syntax is far easier to read and use. In neither case do I use Linq -> SQL

[agolddog]

Me too.

[ventureaaron]

It is the recommended way for SharePoint 2010 CRUD according to "SharePoint 2010 Dev with VS2010" by E. Carter et al. I use it and love having some of that back end taken care of (and i've really grown to like Linq). but as someone else said i use straight up SQL when the going gets tough.

[BrentHolmstrom]

Tried it for a project but quickly had to abandon it. Found it too rigid. If you try using against a many databases. When one database adds a field, it completely breaks querying the table. Though I enjoyed learning about CROSS APPLY from examining it but discovered that it hits a cap where it performs better than anything else in a limited use environment, but once you pass a threshold it takes down systems.