<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.technet.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>Modern .NET Development and The Joy of Simple LINQ to SQL</title><link>http://blogs.technet.com/mscom/archive/2008/04/16/modern-net-development-and-the-joy-of-simple-linq-to-sql.aspx</link><description>Introduction – Modern .NET Development It took me a while to realize it, but Microsoft .NET application development has significantly evolved in the past year and a half. This is not your dad’s .NET . The following releases have added many considerable</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>Modern .NET Development and The Joy of Simple LINQ to SQL</title><link>http://blogs.technet.com/mscom/archive/2008/04/16/modern-net-development-and-the-joy-of-simple-linq-to-sql.aspx#3038143</link><pubDate>Wed, 16 Apr 2008 21:01:47 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3038143</guid><dc:creator>Microsoft.com Operations Team Blog</dc:creator><description>&lt;p&gt;Introduction – Modern .NET Development It took me a while to realize it, but Microsoft .NET application&lt;/p&gt;
</description></item><item><title>re: Modern .NET Development and The Joy of Simple LINQ to SQL</title><link>http://blogs.technet.com/mscom/archive/2008/04/16/modern-net-development-and-the-joy-of-simple-linq-to-sql.aspx#3058727</link><pubDate>Wed, 21 May 2008 21:01:54 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3058727</guid><dc:creator>Mark</dc:creator><description>&lt;p&gt;Good blog. &amp;nbsp;But I'd have to say linq syntax is not intuitive to me and nothing in msdn has helped. &amp;nbsp;I think the problem is you can't do much just from seeing a few examples. &amp;nbsp;You also need to understand the full syntax as well.&lt;/p&gt;</description></item><item><title>re: Modern .NET Development and The Joy of Simple LINQ to SQL</title><link>http://blogs.technet.com/mscom/archive/2008/04/16/modern-net-development-and-the-joy-of-simple-linq-to-sql.aspx#3058752</link><pubDate>Wed, 21 May 2008 21:42:41 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3058752</guid><dc:creator>Eric</dc:creator><description>&lt;p&gt;Hi, Mark. Thanks for the comment. I totally agree with you -- LINQ is not very intuitive to apply. And the examples don't help that much, because it is a deep subject about a sophisticated, powerful .NET feature.&lt;/p&gt;
&lt;p&gt;First you have the many different varieties of LINQ: SQL, DataSet, XML, Objects, Entities. Each one of these seems to have its own nuances and is applicable in different scenarios. You can read about these but actually experimenting seems to be key. The first time I tried to apply LINQ, I did not have much time to explore it, and ended up not using it. In my second run at it, I had more time. But, it took me quite a while to distill what I needed from numerous examples and make enough sense out of it to get the job done. An important factor for me was that I was only reading data, and not writing it. I hear that if you need to read and write, it makes sense to employ the Visual Studio 2008 Object Relational Designer and use LINQ to Entities. The entities end up being logical representations of business objects in your data store.&lt;/p&gt;
&lt;p&gt;MSDN’s “LINQ to SQL: .NET Language-Integrated Query for Relational Data” article could help you. Also, www.linqpad.net is a useful tool for exploring the syntax and the examples are pretty good in there.&lt;/p&gt;
&lt;p&gt;Good luck,&lt;/p&gt;
&lt;p&gt;Eric&lt;/p&gt;</description></item></channel></rss>