Linq to SQL - yes or no...?
-
On many sites I have read that microsoft is not going to add new features to Linq to SQL. So is it dead? From developers point of view should one go for Linq to SQL or Entity Framework?
-
On many sites I have read that microsoft is not going to add new features to Linq to SQL. So is it dead? From developers point of view should one go for Linq to SQL or Entity Framework?
Entity framework is the way to go, I have seen many exciting developments in this field in MS Tech Ed. Also the way virtualisation in WPF and Silverlight is going it would be very handy to know. LINQ to SQL is not completely dead there will always be a use for it, just like datasets ect
Chona1171 Web Developer (C#), Silverlight
-
On many sites I have read that microsoft is not going to add new features to Linq to SQL. So is it dead? From developers point of view should one go for Linq to SQL or Entity Framework?
Since Entity Framework uses LinqToSql I would say it is not dead. Just Microsoft has always done they are moving toward other implementations of the technology.
I know the language. I've read a book. - _Madmatt
-
On many sites I have read that microsoft is not going to add new features to Linq to SQL. So is it dead? From developers point of view should one go for Linq to SQL or Entity Framework?
Starting new projects in Linq2Sql sounds like a mistake, while converting working ones to Entity Framework sounds like a waste of time.
-
On many sites I have read that microsoft is not going to add new features to Linq to SQL. So is it dead? From developers point of view should one go for Linq to SQL or Entity Framework?
The Linq to SQL team has been absorbed by the entity Framework team in Microsoft. I use Linq to SQL in a large project that I am working on that we started years ago. Part of the reason that I have not changed it to EF yet is that we are still on VS2008. The new EF that is in .NET 4 provides alot of the functionality that we use from Linq to SQL, such as lazy loading of objects. This is not in the EF that is included in VS2008 and since our product uses that, we cannot switch over until we move up to .NET 4. Take a look at the features. You did not say if this was using VS2008 or VS2010. For me, Linq to SQL was the better choice in VS2008, but if you are using VS2010, then EF4 is the better path.
Steve Maier
-
On many sites I have read that microsoft is not going to add new features to Linq to SQL. So is it dead? From developers point of view should one go for Linq to SQL or Entity Framework?
I love Linq to SQL for the queries, but it is an absolute dog when doing inserts or updates of very large transaction sets. For example, my application requires doing about 60,000 inserts as a single transaction. Using SqlCommand it takes 20 seconds. Using Linq to SQL it takes 200 seconds. I believe that because of all the checking for Foreign Key integrity it actually grows exponentially as new items are added to the transaction. As for Entity Framework, I am also using VS 2008 and would not want to use Entity Framework until VS 2010 which has a more stable and mature product than the one with VS 2008. Also since ADO gives me so much better performance for my very large transaction set, I don't think the time taken to set up an experiment with Entity Framework is worth the effort. Robert Tanenbaum