<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Choosing between ADO.NET Entity Framework and LINQ to SQL</title><link>http://blogs.msdn.com/b/wriju/archive/2009/03/08/choosing-between-ado-net-entity-framework-and-linq-to-entity.aspx</link><description>As part of my day to job I come across a very common question from the developer community that one should be using LINQ to SQL (L2S) or ADO.NET Entity Framework (EF). 
 
 Earlier I have posted a blog containing the features http://blogs.msdn.com/wriju</description><dc:language>en</dc:language><generator>Telligent Evolution Platform Developer Build (Build: 5.6.50428.7875)</generator><item><title>re: Choosing between ADO.NET Entity Framework and LINQ to SQL</title><link>http://blogs.msdn.com/b/wriju/archive/2009/03/08/choosing-between-ado-net-entity-framework-and-linq-to-entity.aspx#10276334</link><pubDate>Fri, 02 Mar 2012 09:57:48 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:10276334</guid><dc:creator>chungld</dc:creator><description>&lt;p&gt;thank you, this story is very useful for me!&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=10276334" width="1" height="1"&gt;</description></item><item><title>re: Choosing between ADO.NET Entity Framework and LINQ to SQL</title><link>http://blogs.msdn.com/b/wriju/archive/2009/03/08/choosing-between-ado-net-entity-framework-and-linq-to-entity.aspx#10017899</link><pubDate>Mon, 31 May 2010 21:35:11 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:10017899</guid><dc:creator>MikeGale</dc:creator><description>&lt;p&gt;Thanks for that. &amp;nbsp;The L2S vs L2EF debate is still live (2010-06-01). &amp;nbsp;There&amp;#39;s ongoing debate, including ease of use and the wisdom of the &amp;quot;canonical form&amp;quot; used to work with different data providers. &amp;nbsp;A complex area and one size definitely doesn&amp;#39;t fit everybody.&lt;/p&gt;
&lt;p&gt;I put up an experimental online application that looks at the choice.&lt;/p&gt;
&lt;p&gt;It helps work through your own thoughts, with notes, links and an email containing a suggestion graphic.&lt;/p&gt;
&lt;p&gt;An introduction to it is at &lt;a rel="nofollow" target="_new" href="http://decisionz.wordpress.com/2010/04/09/suggestions-for-linq-tool-to-use/"&gt;decisionz.wordpress.com/.../suggestions-for-linq-tool-to-use&lt;/a&gt; (has a link to the live page).&lt;/p&gt;
&lt;p&gt;It guides your own work, doesn&amp;#39;t provide a single recommendation.&lt;/p&gt;
&lt;p&gt;Might be useful to people looking at the choice.&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=10017899" width="1" height="1"&gt;</description></item><item><title>re: Choosing between ADO.NET Entity Framework and LINQ to SQL</title><link>http://blogs.msdn.com/b/wriju/archive/2009/03/08/choosing-between-ado-net-entity-framework-and-linq-to-entity.aspx#10000360</link><pubDate>Wed, 21 Apr 2010 22:30:34 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:10000360</guid><dc:creator>Lead Internet</dc:creator><description>&lt;P&gt;Thanks for the info. It will be nice once this space matures and we don't have to decide on so many different data access options. I've used ado.net, wrote my own custom data access classes, used .netTiers, and Linq to Sql. I'd like to stay ahead of the curve so I'm going to try out the ADO.NET Entity Framework in hopes that this will be around for a while. &lt;/P&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=10000360" width="1" height="1"&gt;</description></item><item><title>re: Choosing between ADO.NET Entity Framework and LINQ to SQL</title><link>http://blogs.msdn.com/b/wriju/archive/2009/03/08/choosing-between-ado-net-entity-framework-and-linq-to-entity.aspx#9829598</link><pubDate>Sat, 11 Jul 2009 17:47:23 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9829598</guid><dc:creator>Latif OZTURK</dc:creator><description>&lt;p&gt;Thank you for sharıng this information with us.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9829598" width="1" height="1"&gt;</description></item><item><title>re: Choosing between ADO.NET Entity Framework and LINQ to SQL</title><link>http://blogs.msdn.com/b/wriju/archive/2009/03/08/choosing-between-ado-net-entity-framework-and-linq-to-entity.aspx#9608051</link><pubDate>Tue, 12 May 2009 23:06:45 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9608051</guid><dc:creator>Chris Lively</dc:creator><description>&lt;p&gt;Your deduction about LINQ to SQL is wrong. Specifically:&lt;/p&gt;
&lt;p&gt;&amp;quot;There has been another concern comes from dev community is that is LINQ to SQL going to retire? Answer to that is no. Microsoft will continue to support L2S and enhance based on customer feedback. Tim Mallalieu clearly have mentioned in his Post that Microsoft will heavily invest into EF and the most wanted features like POCO will be with .NET 4.0. &amp;quot;&lt;/p&gt;
&lt;p&gt;I read his post and the answer to the question is Yes: LINQ to SQL is going away. &amp;nbsp;It is being replaced by LINQ to Entities / EF. &amp;nbsp;He even stated in that post that he wants to know what people use in L2S in order to make sure it is in L2E. &amp;nbsp;&lt;/p&gt;
&lt;p&gt;In short, there isn't a choice. &amp;nbsp;Either skip the whole LINQ thing or embrace the entity framework.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9608051" width="1" height="1"&gt;</description></item><item><title>re: Choosing between ADO.NET Entity Framework and LINQ to SQL</title><link>http://blogs.msdn.com/b/wriju/archive/2009/03/08/choosing-between-ado-net-entity-framework-and-linq-to-entity.aspx#9475385</link><pubDate>Sat, 14 Mar 2009 14:10:50 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9475385</guid><dc:creator>Janus007</dc:creator><description>&lt;P&gt;Well, that's your opinion. I agree with you in that the L2E has many nice features&lt;/P&gt;
&lt;P&gt;"It simplifies the data access and allows me to create conceptual model required for my business."&lt;/P&gt;
&lt;P&gt;-&amp;gt; So does L2S, the conceptual model can be simplified through the use of views.&lt;/P&gt;
&lt;P&gt;Ø &amp;nbsp; &amp;nbsp; &amp;nbsp; EF allows you to handle Many to Many relationship without extra join.&lt;/P&gt;
&lt;P&gt;-&amp;gt; Too bad for L2S, but again... use views :)&lt;/P&gt;
&lt;P&gt;Ø &amp;nbsp; &amp;nbsp; &amp;nbsp; Map related tables into single entity to reduce code complexity.&lt;/P&gt;
&lt;P&gt;-&amp;gt; Yup... they told me so, but it doesn't work succesfully.&lt;/P&gt;
&lt;P&gt;Ø &amp;nbsp; &amp;nbsp; &amp;nbsp; Strong inheritance supports for (Table per hierarchy, subclass and concrete type)&lt;/P&gt;
&lt;P&gt;-&amp;gt; Yup, but then again... isn't that cluttering your layer?&lt;/P&gt;
&lt;P&gt;Ø &amp;nbsp; &amp;nbsp; &amp;nbsp; Consolidation for complex object is very easy.&lt;/P&gt;
&lt;P&gt;-&amp;gt; Not sure what you mean?&lt;/P&gt;
&lt;P&gt;You forgot to mention that if the relational model changes you've to tear down all your tables in the designer and built it up from scratch again - which is something that just works perfectly in L2S.&lt;/P&gt;
&lt;P&gt;L2E performance is poor, not to mention the funny SQL-statements it sometimes produce.&lt;/P&gt;
&lt;P&gt;I think that Microsoft should put a big effort into joining the C#-team (L2S) with the ADO.NET-team (L2E) and then maybe they could produce something useful, as time is now it's frustrating.&lt;/P&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9475385" width="1" height="1"&gt;</description></item><item><title>ADO.NET Entity Framework vs LINQ to SQL</title><link>http://blogs.msdn.com/b/wriju/archive/2009/03/08/choosing-between-ado-net-entity-framework-and-linq-to-entity.aspx#9473180</link><pubDate>Fri, 13 Mar 2009 17:12:15 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9473180</guid><dc:creator>Wriju's BLOG</dc:creator><description>&lt;p&gt;I have been getting a continuous request on what we should be using? LINQ to SQL or ADO.NET Entity Framework?&lt;/p&gt;
&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9473180" width="1" height="1"&gt;</description></item><item><title>re: Choosing between ADO.NET Entity Framework and LINQ to Entity</title><link>http://blogs.msdn.com/b/wriju/archive/2009/03/08/choosing-between-ado-net-entity-framework-and-linq-to-entity.aspx#9465516</link><pubDate>Sun, 08 Mar 2009 14:08:14 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9465516</guid><dc:creator>Pena</dc:creator><description>&lt;P&gt;Or ECO V &lt;A href="http://www.capableobjects.com/" target=_new rel=nofollow&gt;http://www.capableobjects.com/&lt;/A&gt; &lt;/P&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9465516" width="1" height="1"&gt;</description></item><item><title>Choosing between ADO.NET Entity Framework and LINQ to Entity - Wriju's Blog</title><link>http://blogs.msdn.com/b/wriju/archive/2009/03/08/choosing-between-ado-net-entity-framework-and-linq-to-entity.aspx#9465301</link><pubDate>Sun, 08 Mar 2009 12:17:15 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9465301</guid><dc:creator>DotNetShoutout</dc:creator><description>&lt;p&gt;Thank you for submitting this cool story - Trackback from DotNetShoutout&lt;/p&gt;
&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9465301" width="1" height="1"&gt;</description></item><item><title>Click &amp;amp; Solve &amp;raquo;  Choosing between ADO.NET Entity Framework and LINQ to Entity </title><link>http://blogs.msdn.com/b/wriju/archive/2009/03/08/choosing-between-ado-net-entity-framework-and-linq-to-entity.aspx#9464714</link><pubDate>Sun, 08 Mar 2009 06:35:58 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9464714</guid><dc:creator>Click &amp;amp; Solve &amp;raquo;  Choosing between ADO.NET Entity Framework and LINQ to Entity </dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://www.clickandsolve.com/?p=19339"&gt;http://www.clickandsolve.com/?p=19339&lt;/a&gt;&lt;/p&gt;
&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9464714" width="1" height="1"&gt;</description></item></channel></rss>