Project Description
Reverse engineers an existing database and generates EntityFramework Code First POCO classes, DbContext and Configuration mappings
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. http://visualstudiogallery.msdn.microsoft.com/ee4fcff9-0c4c-4179-afd9-7a2fb90f5838
Done, but not yet released to Nuget:
- If a field has a default contrainst of GetDate(), add DateTime.Now() in the ctor for the field.
Up-comming cool things:
- Add support for the datetimeoffset type, including support for the default constraint sysdatetimeoffset().
- 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.
- Add Resharper naming comment.
- 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
- Functions
- Views
- Mappings should be marked internal. Requested by Hobbes Pirakitti
- Separate files for DbContext, Mappings, and POCO'. Requested by Hobbes Pirakitti
- Easy way to separate each POCO/mapping into its own file. Requested by Hobbes Pirakitti
- Ability to Have Entity or Types generated in it's own namespace and or a project. Requested by spatemp
- Ability to add WCF(DataMember, DataContract attributes) support on Entity. Requested by spatemp
- If all of your table name begins with some string(AB_Orders), then remove that string as part of Entity name(Orders). Requested by spatemp
- 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)