tag:blogger.com,1999:blog-11646261.post3398745692797919508..comments2024-01-02T00:43:44.344-08:00Comments on OakLeaf Systems: “Data Dilemma” Cover Story for Redmond Developer News’ July 15 IssueRoger Jennings (--rj)http://www.blogger.com/profile/01700526164060680385noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-11646261.post-86562292970027359682008-07-17T09:38:00.000-07:002008-07-17T09:38:00.000-07:00@anon,I'm not sanguine about the future of LINQ to...@anon,<BR/><BR/>I'm not sanguine about the future of LINQ to SQL. The SQL Server Data Programming group is placing all their bets on Entity Framework and devoting little or no energy to LINQ to SQL. (One dev I know is working on LINQ to SQL, but I have no knowledge of what he's working on.)<BR/><BR/>See http://oakleafblog.blogspot.com/2008/05/is-adonet-team-abandoning-linq-to-sql.html for more Roger Jennings (--rj)https://www.blogger.com/profile/01700526164060680385noreply@blogger.comtag:blogger.com,1999:blog-11646261.post-27677706516612063282008-07-17T09:09:00.000-07:002008-07-17T09:09:00.000-07:00Roger, enjoy your blog and looking forward to your...Roger, enjoy your blog and looking forward to your upcoming book on LINQ and the EF. Will it cover LINQ to SQL also (I don't want to make any assumptions). I prefer LINQ to SQL over LINQ to EF, and really hope LINQ to SQL doesn't get shelved in favor of the EF. It would have been nice if Microsoft opened up the provider/dialect to other database vendors for LINQ to SQL. LINQ to SQL just feelsAnonymousnoreply@blogger.com