I'm not sure if this belongs in one of the data forums or if it can fit in this forum, but I was wondering if anyone sees any significant changes to LinqToSQL and Entity Framework in 4.0.
Alot was written about how LinqToSQL is dead in favor of Entity Framework. Is it still in 4.0? Did it get any improvements or is it truely dead?
I have read about some of the changes and improvements to Entity Framework in 4.0:
http://blogs.msdn.com/scothu/archive/2009/10/20/data-enhancements-in-net-4-visual-studio-2010-beta-2.aspx
The pluralize/singularize and foreign key features sound good and were both things I missed when using Entity Framework. Any other features that bring the ease of LinqToSQL into Entity Framework? Should we now look forward to not using LinqToSQL?
That is good. I wonder if they are going to make any improvements to it? For me it's not interesting using something that you know won't be improved upon in the future. If EF is the direction and it works I'll go there.
From what I'm reading the EF is incorporating a lot of what people liked about linq to sql.
I just attended the VSLive! developer conference in Orlando, FL this month and there were several comments made on this very topic. It was stated often that while Linq to SQL is not dead and will not be depricated or anything like that, there is no actively
assigned team at Microsoft enhancing or working on new features for it. However, Microsoft has placed full efforts into the Entity Framework and seems to be the flagship data access method going forward.
It is also impotant to note that while Linq to SQL might have hit a wall in a sense, Linq itself has
not. Linq to Objects, Linq to XML, etc. are still very useful and will continue to be for some time.
Member
749 Points
245 Posts
LinqToSQL and Entity Framework in 4.0
Oct 21, 2009 07:32 PM|uid257770|LINK
I'm not sure if this belongs in one of the data forums or if it can fit in this forum, but I was wondering if anyone sees any significant changes to LinqToSQL and Entity Framework in 4.0.
Alot was written about how LinqToSQL is dead in favor of Entity Framework. Is it still in 4.0? Did it get any improvements or is it truely dead?
I have read about some of the changes and improvements to Entity Framework in 4.0:
http://blogs.msdn.com/scothu/archive/2009/10/20/data-enhancements-in-net-4-visual-studio-2010-beta-2.aspx
The pluralize/singularize and foreign key features sound good and were both things I missed when using Entity Framework. Any other features that bring the ease of LinqToSQL into Entity Framework? Should we now look forward to not using LinqToSQL?
LinqToSQL Entity Framework
Contributor
2828 Points
1308 Posts
Re: LinqToSQL and Entity Framework in 4.0
Oct 21, 2009 07:35 PM|mpaterson|LINK
Microsoft has repeatedly said that they will not get rid of LINQ To SQL.
Member
749 Points
245 Posts
Re: LinqToSQL and Entity Framework in 4.0
Oct 21, 2009 10:20 PM|uid257770|LINK
That is good. I wonder if they are going to make any improvements to it? For me it's not interesting using something that you know won't be improved upon in the future. If EF is the direction and it works I'll go there.
From what I'm reading the EF is incorporating a lot of what people liked about linq to sql.
I found another link:
http://blogs.msdn.com/adonet/archive/2009/10/19/vs2010-and-net-framework-beta-2-announced.aspx
Sounds really interesting. I will try it again when it comes out. At least it's not too difficult to change from linq to sql to EF.
Star
12060 Points
2740 Posts
Re: LinqToSQL and Entity Framework in 4.0
Oct 26, 2009 11:10 AM|atconway|LINK
I just attended the VSLive! developer conference in Orlando, FL this month and there were several comments made on this very topic. It was stated often that while Linq to SQL is not dead and will not be depricated or anything like that, there is no actively assigned team at Microsoft enhancing or working on new features for it. However, Microsoft has placed full efforts into the Entity Framework and seems to be the flagship data access method going forward.
It is also impotant to note that while Linq to SQL might have hit a wall in a sense, Linq itself has not. Linq to Objects, Linq to XML, etc. are still very useful and will continue to be for some time.