Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I read somewhere on the ‘net that Microsoft is considering moving away from LINQ-To-SQL in its current form as it wasn’t very successful.
I want as many opinions on this as possible as I’m new to .NET and want to choose the best possible route for where I work.
No, not LINQ per se. The ‘Language Integrated Query’ is here to stay.
There’s some talk about MS giving up on ‘Linq-to-SQL’ (the SQLServer-only database version of LINQ) in favour of the ADO.NET Entity Framework, but even that’s still a bit unclear.
See this post in the MS ADO.NET team blog and these comments here by Oren Eini and David Hayden.
And while I think Linq-To-Sql probably won’t receive big updates anymore, I highly doubt it’ll be physically removed from the product, so there’s always opportunity for third-party developers to step in and make it great nonetheless!