c# - EF Model First and Database First Alternatives? -

since msft has officially abandoned model first , database first, have alternative suggestions functionality? 1 considering devart entity developer. can else suggest other alternatives should consider?

a while before msft announced dropping database first, considering using sparx ea maintain database, use ef database first update model database, refuse acknowledge need generate code first design model though database first no longer supported ef. ea generate poco classes, not codefirst variant, , don't want update hand.

as per link, not removing database first design, code-first name means database represented set of poco c# objects, rather xml + designer.

they have remvoed designer , .edmx file. can still `reverse engineer database create entities.

from link:

for code first can re-run reverse engineer process , have regenerate model. works fine in basic scenarios, have careful how customize model otherwise changes reverted when code re-generated. there customizations difficult apply without editing scaffolded code.

them removing designer, , making ef code-first only, not mean have create entities first in c# have them generate database. means database mapped via poco's rather .edmx.

and believe me, .edmx + designer nothing problems!!!!

if not going happy reverse-engineering results, or adding new tables/relationships via code, i'm create fancy drag+drop designer 3rd party add-on. me + of devs know, designer beginners, start doing or customizing it, have better, cleaner, easier understand control in code via annotations + fluent mappings.