To get the prototype for a project up and running as quickly as possible, I used LINQ to SQL for data persistence.
Now the project is more mature and I'm running into concurrency limitations with LINQ to SQL. Since its not a true ORM, nor was it meant for enterprise use, I'd like to replace all the LINQ to SQL work with Entity Framework persistence.
What's involved in this? Can any of my LINQ to SQL work be retooled for EF? Am I going to have to start over with EF from scratch? Where do I start? Any helpful links or advice?
Best Answer
Many people are doing the same conversion. There is a template that you can use to do the conversion here http://blogs.msdn.com/b/efdesign/archive/2009/08/13/linq-to-sql-to-entity-framework-conversion-template.aspx