Keep using Linq-to-SQL (deprecated?) or migrate to Entity Framework v6

by Jordy van Eijk   Last Updated May 14, 2018 13:05 PM

I'm a C# software developer and the problem we are facing is. We have a WPF frontend application and an WCF backend applicaiton talking to Azure SQL server. More and more of the application is parts of the Azure environment. Our current DataLayer is using Linq-to-SQL for quite some time now 2010 till now (2018). There are a couple of people in the development team that want to migrate the application to Entity Framework v6 (6.2) but other people keep saying we need to keep it like it is now because it is working. We are still actively developing the application and will probably be doing so for many years to come.

Now the question is do we migrate to Entity Framework v6 or should we keep the old Linq-to-SQL DataLayer.

I hope some of you have also had the same issues / questions lately and can give me some advice on what to do!

I hope someone can create new tag Linq-to-Sql i dont have the privilage on this site and add it to the question tags

Some extra background information on techniques we use:

  • .net Framework 4.7.1
  • C#
  • Azure SQL server (elastic pools)
  • Azure storage
  • Redis-cache


Related Questions


Fetching latest time from date field

Updated June 14, 2018 10:05 AM