http://blogs.msdn.com/jongallant/archive/tags/linq/default.aspxTags: linqen-USCommunityServer 2.1 SP1 (Build: 61025.2)http://blogs.msdn.com/jongallant/archive/2008/04/17/short-and-sweet-silverlight-2-0-linq-and-wcf-in-5-minutes-video.aspxThu, 17 Apr 2008 19:39:44 GMT91d46819-8472-40ad-a661-2c78acb4018c:8403701jongallant6http://blogs.msdn.com/jongallant/comments/8403701.aspxhttp://blogs.msdn.com/jongallant/commentrss.aspx?PostID=8403701http://blogs.msdn.com/jongallant/rsscomments.aspx?PostID=8403701Download Source This is the first video in my new "Short and Sweet" video series. I'm going to continue with Silverlight, LINQ and WCF path for the series. Please ping me if you have an idea for a future video. This video takes you through the minimum...(<a href="http://blogs.msdn.com/jongallant/archive/2008/04/17/short-and-sweet-silverlight-2-0-linq-and-wcf-in-5-minutes-video.aspx">read more</a>)<img src="http://blogs.msdn.com/aggbug.aspx?PostID=8403701" width="1" height="1">asp.netc#.netsqlsilverlightlinqvideoshttp://blogs.msdn.com/jongallant/archive/2007/12/02/linq-sequence-contains-no-elements-invalidoperationexception-when-calling-single.aspxSun, 02 Dec 2007 11:09:00 GMT91d46819-8472-40ad-a661-2c78acb4018c:6641348jongallant8http://blogs.msdn.com/jongallant/comments/6641348.aspxhttp://blogs.msdn.com/jongallant/commentrss.aspx?PostID=6641348http://blogs.msdn.com/jongallant/rsscomments.aspx?PostID=6641348If you call Single to get an object from your DB and the object doesn't exist you will get an InvalidOperationException. return this .DataContext.MemberDaos.Single(m =&gt; m.MemberID == id); Instead of Single, use SingleOrDefault, which will return null...(<a href="http://blogs.msdn.com/jongallant/archive/2007/12/02/linq-sequence-contains-no-elements-invalidoperationexception-when-calling-single.aspx">read more</a>)<img src="http://blogs.msdn.com/aggbug.aspx?PostID=6641348" width="1" height="1">solutionc#linqhttp://blogs.msdn.com/jongallant/archive/2007/12/01/linq-add-renamed-to-insertonsubmit.aspxSun, 02 Dec 2007 07:19:00 GMT91d46819-8472-40ad-a661-2c78acb4018c:6638887jongallant6http://blogs.msdn.com/jongallant/comments/6638887.aspxhttp://blogs.msdn.com/jongallant/commentrss.aspx?PostID=6638887http://blogs.msdn.com/jongallant/rsscomments.aspx?PostID=6638887If you are using LINQ to insert data with RTM bits you won't find the Add method on the DataContext post Beta2. Use the InsertOnSubmit method instead....(<a href="http://blogs.msdn.com/jongallant/archive/2007/12/01/linq-add-renamed-to-insertonsubmit.aspx">read more</a>)<img src="http://blogs.msdn.com/aggbug.aspx?PostID=6638887" width="1" height="1">solutionc#linqhttp://blogs.msdn.com/jongallant/archive/2007/11/25/linq-and-web-application-connection-strings.aspxSun, 25 Nov 2007 23:52:00 GMT91d46819-8472-40ad-a661-2c78acb4018c:6522285jongallant9http://blogs.msdn.com/jongallant/comments/6522285.aspxhttp://blogs.msdn.com/jongallant/commentrss.aspx?PostID=6522285http://blogs.msdn.com/jongallant/rsscomments.aspx?PostID=6522285It's usually a good idea to seperate Biz Layer Objects and Data Access Objects into seperate assemblies, but when you do that and use LINQ to SQL (.dbml) files the DataContext object default ctor uses the Settings file that is automattically generated...(<a href="http://blogs.msdn.com/jongallant/archive/2007/11/25/linq-and-web-application-connection-strings.aspx">read more</a>)<img src="http://blogs.msdn.com/aggbug.aspx?PostID=6522285" width="1" height="1">asp.netc#web applicationslinq