.NET Core command-line (CLI) tool to generate Entity Framework Core model from an existing database.
- Entity Framework Core database first model generation
- Safe regeneration via region replacement
- Safe Renaming via mapping file parsing
- Optionally generate read, create and update models from entity
- Optionally generate validation and object mapper classes
Entity Framework Core Generator documentation is available via Read the Docs
To install EntityFrameworkCore.Generator tool, run the following command in the console
dotnet tool install --global EntityFrameworkCore.GeneratorAfter the tool has been install, the efg command line will be available. Run efg --help for command line options
Entity Framework Core Generator (efg) creates source code files from a database schema. To generate the files with no configuration, run the following
efg generate -c <ConnectionString>Replace <ConnectionString> with a valid database connection string.
The generate command will create the follow files and directory structure by default. The root directory defaults to the current working directory. Most of the output names and locations can be customized in the configuration file
The EntityFramework DbContext file will be created in the root directory.
The entities directory will contain the generated source file for entity class representing each table.
The mapping directory contains a fluent mapping class to map each entity to its table.
The initialize command is used to create the configuration yaml file and optionally set the connection string. The configuration file has many options to configure the generated output. See the configuration file documentation for more details.
The following command will create an initial generation.yaml configuration file as well as setting a user secret to store the connection string.
efg initialize -c <ConnectionString>When a generation.yaml configuration file exists, you can run efg generate in the same directory to generate the source using that configuration file.
Entity Framework Core Generator supports safe regeneration via region replacement and source code parsing. A typical workflow for a project requires many database changes and updates. Being able to regenerate the entities and associated files is a huge time saver.
All the templates output a region on first generation. On future regeneration, only the regions are replaced. This keeps any other changes you've made to the source file.
Example of a generated entity class
public partial class Status
{
public Status()
{
#region Generated Constructor
Tasks = new HashSet<Task>();
#endregion
}
#region Generated Properties
public int Id { get; set; }
public string Name { get; set; }
public string Description { get; set; }
public int DisplayOrder { get; set; }
public bool IsActive { get; set; }
public DateTimeOffset Created { get; set; }
public string CreatedBy { get; set; }
public DateTimeOffset Updated { get; set; }
public string UpdatedBy { get; set; }
public Byte[] RowVersion { get; set; }
#endregion
#region Generated Relationships
public virtual ICollection<Task> Tasks { get; set; }
#endregion
}When the generate command is re-run, the Generated Constructor, Generated Properties and Generated Relationships regions will be replace with the current output of the template. Any other changes outside those regions will be safe.
In order to capture and preserve Entity, Property and DbContext renames, the generate command parses any existing mapping and DbContext class to capture how things are named. This allows you to use the full extend of Visual Studio's refactoring tools to rename things as you like. Then, when regenerating, those changes won't be lost.
Entity Framework Core Generator supports the following databases.
- SQL Server
- PostgreSQL
- MySQL
- Sqlite
The provider can be set via command line or via the configuration file.
Set via command line
efg generate -c <ConnectionString> -p <Provider>Set in configuration file
database:
connectionString: 'Data Source=(local);Initial Catalog=Tracker;Integrated Security=True'
provider: SqlServerThe database schema is loaded from the metadata model factory implementation of IDatabaseModelFactory. Entity Framework Core Generator uses the implemented interface from each of the supported providers similar to how ef dbcontext scaffold works.
Entity Framework Core Generator supports generating Read, Create and Update view models from an entity. Many projects rely on view models to shape data. The model templates can be used to quickly get the basic view models created. The model templates also support regeneration so any database change can easily be sync'd to the view models.
- upgrade to .net 8
- add option to turn off temporal table mapping
- add rowversion options, ByteArray|Long|ULong
- add script template merge
- add support for navigation property renames
- update generated query methods to support CancellationToken
- add support for temporal tables
- add regex clean support for table and column names
- add support for nullable reference types
- upgrade projects to .net 6
- Breaking change to generated mapping constants
TableNameis nowTable.NameTableSchemais nowTable.SchemaColumn{Name}is nowColumns.{Name}
- add additional automapper for read model to update model
- Add
Table.NameandTable.Schemavariable support in yaml configuration. - Add entity name option to control the name of the entity. Leave blank to use previous generate logic. Set under the entity -> name yaml settings.
- Add exclude table support. Set under the database -> exclude yaml settings.
- Include and Exclude expression can now be
exactorregex. When exact, will be direct string match. When regex, will use regular expression to match. Default is regex for legacy support.
- Add external script template support
- Misc bug fixes
- Add support for Entity Framework Core 3.0
- Add provider support for PostgreSQL, MySQL and Sqlite
- Add View support
- Add alias to commands, can use
efg genforefg generateandefg initforefg initialize - Fix bug where base class for Entity was placed in wrong location
- Fix misc sorting issue that caused needless source control changes