“Porting” Entity Framework’s EDMX files to .Net Core

We’ve all been there, our manager asks us to port a 10 year old legacy app, built with all the wrong design patterns from .Net Framework’s Entity Framework to .Net Core – Just to realise that .Net Core’s implementation of Entity Framework is literally a completely different library. It’s basically the equivalent of “porting” your database layer from Python to Lisp. You might as well give up. SHIFT + DELETE the folder with your backend code, and start the project entirely from scratch is my advice to you.

However, the good news is that I’ve got a tool that allows you to reignite your backend, extremely rapidly, assuming you have a ton of endpoints simply doing CRUD stuff + authorisation. If this is true for your solution, you can literally recreate an entirely new .Net Core based backend in seconds, without having to bother about how to change from your EDMX file’s syntax to the new attributed version of .Net Core’s Entity Framework. Watch the video to understand what I am talking about 🙂

Leave a Reply

Please log in using one of these methods to post your comment:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.