LINQ to SQL - DNR?
-
Regarding the previous post. Due to a long vacation with no cellphones/computers I am a little out-of-it. What's happening with LINQ and Linq-to-SQL? Is it still worth developing our new DAL on or should we reconsider? What's all this talk that LINQ-to-SQL is dead?
-
Regarding the previous post. Due to a long vacation with no cellphones/computers I am a little out-of-it. What's happening with LINQ and Linq-to-SQL? Is it still worth developing our new DAL on or should we reconsider? What's all this talk that LINQ-to-SQL is dead?
MS is going to replace it with Entity Framework.
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001 -
MS is going to replace it with Entity Framework.
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001It looks like the same team is working on Linq2Sql and Ado Framwork and only one will win (ADO EF)they claim Linq2Sql will still be there and they will keep it current only time will tell I have played with both and find Linq2 Sql much friendlier .If you add all the tables of a db into one linq2sql designer you get a similar effect as EF but I must admit the "codeless" nature of ADO Ef makes it very attractive.Alsso in linq2 sql you have to manage your own entity states There is not much info in a readable form hence my post below
Mike
-
Regarding the previous post. Due to a long vacation with no cellphones/computers I am a little out-of-it. What's happening with LINQ and Linq-to-SQL? Is it still worth developing our new DAL on or should we reconsider? What's all this talk that LINQ-to-SQL is dead?
I have been developing with LINQ to SQL for about six months now on my website www.myfitnessjournal.com I use Linq to Sql for the DAL and have had no real issues at all. It has been great to work with although there were some tricks to things like transactions and updating data using WCF services but when I tried EF at the beginning of the project I found that there were some pretty important things missing that I needed, also I was using SQL server for the database so Linq to Sql was great for that. If I remember correctly some of the Date methods and String comparisons weren't completely supported yet in EF. Of course all I hear lately is that EF will eventually replace L2S but if you wait for that you can be certain some other mystery project will be almost ready to replace EF. So in other words I just used the tool that worked better for me. All of these things have a decent learning curve but if you learn L2S you won't have any problem moving to EF later.
Nick Lecrenski Founder/Lead Developer http://www.myfitnessjournal.com
-
Regarding the previous post. Due to a long vacation with no cellphones/computers I am a little out-of-it. What's happening with LINQ and Linq-to-SQL? Is it still worth developing our new DAL on or should we reconsider? What's all this talk that LINQ-to-SQL is dead?
I have also read the LINQ-to-SQL might not survive so I wouldn't build a DAL in either just yet. For now, ADO.Net is perfectly capable. Just take a wait and see approach. I often use LINQ-to-SQL for calling stored procs. Nothing is easier then dragging a stored proc on to the designer and getting your method to call it created for you. But I wouldn't create a full blown DAL.
I didn't get any requirements for the signature
-
I have been developing with LINQ to SQL for about six months now on my website www.myfitnessjournal.com I use Linq to Sql for the DAL and have had no real issues at all. It has been great to work with although there were some tricks to things like transactions and updating data using WCF services but when I tried EF at the beginning of the project I found that there were some pretty important things missing that I needed, also I was using SQL server for the database so Linq to Sql was great for that. If I remember correctly some of the Date methods and String comparisons weren't completely supported yet in EF. Of course all I hear lately is that EF will eventually replace L2S but if you wait for that you can be certain some other mystery project will be almost ready to replace EF. So in other words I just used the tool that worked better for me. All of these things have a decent learning curve but if you learn L2S you won't have any problem moving to EF later.
Nick Lecrenski Founder/Lead Developer http://www.myfitnessjournal.com
I am developing my DAL in L2S and so far it's been great! I hear it's dying, yet the "replacement" EF is not yet ready.
nlecren wrote:
So in other words I just used the tool that worked better for me.
I'm not going to stop with L2S, just because some new half finished technology MIGHT replace it. Rumours or not! Like you said, once I have L2S down, switching to EF in the future shouldn't be to hard!
-
Regarding the previous post. Due to a long vacation with no cellphones/computers I am a little out-of-it. What's happening with LINQ and Linq-to-SQL? Is it still worth developing our new DAL on or should we reconsider? What's all this talk that LINQ-to-SQL is dead?
I think the focus of L2S now is for smaller apps where the full blown EF would be overkill. I am not sure what they have planned for L2S, but with their lazy object loading which can cause thousands of SQL calls if a person is not paying attention and for their non-existant support for disconnected entities, they could find it on the chopping block in the future. That said, I still use it and work around its short comings. I would use it for a DAL, but I might consider table adapters and Datasets with LINQ handling my sorting, filtering and grouping needs.
Rocky <>< Recent Blog Post: Netflix coming straight to HDTV! Thinking about Silverlight? www.SilverlightCity.com
-
Regarding the previous post. Due to a long vacation with no cellphones/computers I am a little out-of-it. What's happening with LINQ and Linq-to-SQL? Is it still worth developing our new DAL on or should we reconsider? What's all this talk that LINQ-to-SQL is dead?
Linq2Sql does what it needs to do. They're going to bloat up the Entity framework with all the missing/requested features so that it becomes msHibernate. We're still going to use Linq2Sql at work because we don't need a true ORM, many-to-many relationships or entities in our DAL. *knock on wood*
Todd Smith
-
Regarding the previous post. Due to a long vacation with no cellphones/computers I am a little out-of-it. What's happening with LINQ and Linq-to-SQL? Is it still worth developing our new DAL on or should we reconsider? What's all this talk that LINQ-to-SQL is dead?
When evaluating any technology the first question should always be "what can this do to benefit the end users of my software". If the answer is nothing then you have discovered everything you need to know about that technology and can move on to more important things. LINQ to SQL is dead. It was stillborn. All of LINQ should be relegated to a watery grave somewhere. It's sole purpose in life seems to be to make code more dense and unreadable than it is already and it offers nothing for the end user. It's a great time waster / hobby / geek endeavour if you are an ivory tower type that isn't working in the trenches, I'll give it that.
"It's so simple to be wise. Just think of something stupid to say and then don't say it." -Sam Levenson
-
When evaluating any technology the first question should always be "what can this do to benefit the end users of my software". If the answer is nothing then you have discovered everything you need to know about that technology and can move on to more important things. LINQ to SQL is dead. It was stillborn. All of LINQ should be relegated to a watery grave somewhere. It's sole purpose in life seems to be to make code more dense and unreadable than it is already and it offers nothing for the end user. It's a great time waster / hobby / geek endeavour if you are an ivory tower type that isn't working in the trenches, I'll give it that.
"It's so simple to be wise. Just think of something stupid to say and then don't say it." -Sam Levenson
That is some of the best advice I've seen in a long time - gauging decisions based on customers/users. I spend endless hours trying to explain that to people, but I've not been able to describe it as succinctly as that. In a surprising twist though, LINQ actually did give our end users some tangible benefits, so yay!
