http://weblogs.asp.net/marksmith/archive/tags/LINQ/default.aspxTags: LINQenCommunityServer 2007 SP1 (Build: 20510.895)http://weblogs.asp.net/marksmith/archive/2008/01/25/linq.aspxFri, 25 Jan 2008 12:57:00 GMTc06e2b9d-981a-45b4-a55f-ab0d8bbfdc1c:5650099ca8msmca8msm9http://weblogs.asp.net/marksmith/rsscomments.aspx?PostID=5650099http://weblogs.asp.net/marksmith/commentapi.aspx?PostID=5650099http://weblogs.asp.net/marksmith/archive/2008/01/25/linq.aspx#commentsI have mixed feelings about LINQ. I don't want it interfering with my database, and running queries against it so I think I'll be sticking to stored procedures for this type of access. However, there are also cases where I think it is very useful. Here...(<a href="http://weblogs.asp.net/marksmith/archive/2008/01/25/linq.aspx">read more</a>)<img src="http://weblogs.asp.net/aggbug.aspx?PostID=5650099" width="1" height="1">ASP.NETLINQ