To obtain the prototype for any project ready to go as rapidly as you possibly can, I made use of LINQ to SQL for data persistence.
The project is much more mature and I am encountering concurrency restrictions with LINQ to SQL. Since it is not a genuine ORM, nor maybe it was intended for enterprise use, Let me replace all of the LINQ to SQL use Entity Framework persistence.
What's involved with this? Can any one of my LINQ to SQL work be retooled for EF? Can i need to begin again with EF on your own? Where will i start? Any useful links or advice?
So many people are doing exactly the same conversion. There's a template which you can use to complete the conversion here http://blogs.msdn.com/b/efdesign/archive/2009/08/13/linq-to-sql-to-entity-framework-conversion-template.aspx
This can be a fairly hard problem and among the primary reasons I've been suggesting people avoid LinqToSql for a long time. Microsoft doesn't want people using LinqToSql.
Your best choice will probably begin again and reuse code when/if you're able to (a number of your Linq queries may translate almost one for just one instantly, but even that is not a sure factor).
LinqToSql is really a true, but feature poor, ORM. LinqToSql can be utilized in the enterprise by individuals who do not require advanced ORM features.
You are not likely alone who'll go lower this path (attempting to "upgrade" from LinqToSql to EntityFramework), but it is not obvious at this time if there's an industry need permanently pedaling to aid this type of migration.
Given Microsoft's direction altering on data access every 2 yrs approximately for over a decade now, you might want to consider NHibernate instead of Entity Framework (if you're concerned about Microsoft "sunsetting" Entity Framework like they did to LinqToSql).