Wednesday, November 28, 2018

Migrating to EF from homemade ORM.

I've got a fairly large .net webform project that uses a very old ORM designed by a programmer that no longer works here. It runs a query on the database to get the table information, reads in a text file as a template that holds generic data access properties for each table and its fields and stores them all in a single file in the project. When we create a new table, we run the project, click a button it runs the querys/reads the template and updates this one file. So after years of doing this that one file has gotten fairly large.

I was thinking about proposing a project to convert this to using entity framework. I'm thinking this would be a good direction to take our project, but as a fairly new dev how do I make that argument? What would be some of the benefits to EF over this method?

Migrating to EF from homemade ORM. Click here
  • Blogger Comment
  • Facebook Comment

0 comments:

Post a Comment

The webdev Team