Reverse engineers an existing database and generates EntityFramework Code First POCO classes, DbContext and Configuration mappings.
Currently only works for SQL Server.
This has now been made into a visual studio extension. See documentation tab for further details.
Head over to here to watch a video on how it works.
Up-comming cool things (not in any particular order):
- Add an option to allow the stripping of the table name from the field name. i.e. if the table name is sales_person_order, and a field is called sales_person_order_id, the field would be called ID.
- Non dbo. schemas are currently pre-pended to the table name. ie, Events.SalesOrder are called Events_SalesOrder. It would be better to put these schemas in their own namespace. i.e. Events, so to reference the table with Events.SalesOrder is more natural
- Support the following (with immutable classes for results):
- Stored procedures
- Separate files for DbContext, Mappings, and POCO'. Requested by
- If all of your table name begins with some string(AB_Orders), then remove that string as part of Entity name(Orders). Requested by
- Pluralize the names of the dbset properties on the DataContext. You shouldbe able to use this library to do it:
Microsofts Pluralization Service. Requested by Tony Broodie (ByBox)
- Make it work with other databases. Requested by
- Add ability to have it unit testable. Requested by Simon Dudley.
- Add ability to deactivate camel casing and leave the field names untouched. Requested by
- Add ability to generate data annotations. Add this as an option in the .tt file. Requested by