In 2017, the best way to migrate an entity framework application from using EDMX while maintaining relationships

I saw some old questions asking the same thing ( Tool to convert Entity Framework EDMX to Code First ), but most in 2009-2014 ( EF "First Model": Create an object in edmx and db table from a class? / How to create Entity Framework 6.x POCO classes with display from the EDMX file? ), So I would like to ask if the situation is better in 2017!

We have EDMX, which we have already installed to use the DbContext generator - this gives a cleaner POCO and a more compact context derived from DbContext and not from the now ancient ObjectContext, but it would like to completely destroy the (completely unmergeable) edmx, nevertheless while maintaining many different relationships between the 60 odd objects that we have. By simply deleting existing tt templates, it loses all the entity relationship data.

Is there now a tool or methodology that could help achieve this? I can’t believe that Microsoft itself did not release the tool (disabled powertools, since I believe that they do not generate relationships)

+5
source share

Source: https://habr.com/ru/post/1270269/


All Articles