StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>IMO, not at the moment.</p> <p>It is clear (from <a href="http://blogs.msdn.com/adonet/archive/2008/10/31/clarifying-the-message-on-l2s-futures.aspx" rel="nofollow noreferrer">recent announcements</a> especially) that EF is in for some heavy revisions as the "<a href="http://codebetter.com/blogs/ian_cooper/archive/2008/11/03/linq-to-sql-ef-and-the-thunderdome-solution.aspx" rel="nofollow noreferrer">thunderdome</a>" scenario plays out between LINQ-to-SQL and EF. Whatever happens, EF (in a few years) will almost certainly look quite different to EF today. Or certainly "different enough" ;-p</p> <p>As such, my view is: stick with simple. And simple is LINQ-to-SQL.</p> <p>I don't see much benefit learning a notoriously complex system if I know it is going to change very soon.</p> <p>And I'm 100% with you on LINQ-to-SQL ;-p</p> <p>If I needed something more than LINQ-to-SQL right now, I'd look at <a href="http://www.nhibernate.org/" rel="nofollow noreferrer">NHibernate</a> or maybe <a href="http://www.llblgen.com/" rel="nofollow noreferrer">LLBLGen Pro</a>.</p> <p>(<strong>edit</strong> - as an update, my position has softened a little bit, <a href="http://marcgravell.blogspot.com/2008/12/entity-framework-in-reality.html" rel="nofollow noreferrer">here</a> and <a href="http://marcgravell.blogspot.com/2009/03/back-to-coal-face.html" rel="nofollow noreferrer">here</a> - but I'm still using LINQ-to-SQL as my primary tool; also - LINQ-to-SQL <a href="http://marcgravell.blogspot.com/2009/02/linq-to-sql-not-quite-dead-yet.html" rel="nofollow noreferrer">isn't quite dead yet</a> ;-p).</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload