<?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>Linq: Why and Its Contemporary</title><link>http://blogs.msdn.com/b/wriju/archive/2007/05/17/linq-why-and-its-contemporary.aspx</link><description>Why LINQ (or other components of Linq). One of the major reasons is that to address the mismatch between relational data domain and object domain. Database was more comfortable for developers from SQL world and they were no where in object domain. Please</description><dc:language>en</dc:language><generator>Telligent Evolution Platform Developer Build (Build: 5.6.50428.7875)</generator><item><title>Copyright Revewals &amp;raquo; Wriju&amp;#8217;s BLOG : Linq: Why and Its Contemporary</title><link>http://blogs.msdn.com/b/wriju/archive/2007/05/17/linq-why-and-its-contemporary.aspx#8343923</link><pubDate>Sun, 30 Mar 2008 04:51:04 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8343923</guid><dc:creator>Copyright Revewals » Wriju’s BLOG : Linq: Why and Its Contemporary</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://copyrightrenewalsblog.info/wrijus-blog-linq-why-and-its-contemporary/"&gt;http://copyrightrenewalsblog.info/wrijus-blog-linq-why-and-its-contemporary/&lt;/a&gt;&lt;/p&gt;
&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=8343923" width="1" height="1"&gt;</description></item></channel></rss>