CatFactory it's a scaffolding engine for .NET Core built in C#.
The concept behind CatFactory is import an existing database from a SQL Server instance and with that representation in memory for database scaffold code for specific technology.
Code sample:
// Create database factory
var databaseFactory = new SqlServerDatabaseFactory
{
DatabaseImportSettings = new DatabaseImportSettings
{
ConnectionString = "server=(local);database=Store;integrated security=yes;",
Exclusions =
{
"dbo.sysdiagrams"
}
}
};
// Import database
var database = databaseFactory.Import();
// Create instance of Entity Framework Core project
var project = new EntityFrameworkCoreProject
{
Name = "Store",
Database = database,
OutputDirectory = "C:\\Temp\\CatFactory.EntityFrameworkCore\\Store"
};
// Apply settings for Entity Framework Core project
project.GlobalSelection(settings =>
{
settings.ForceOverwrite = true;
settings.AuditEntity = new AuditEntity("CreationUser", "CreationDateTime", "LastUpdateUser", "LastUpdateDateTime");
settings.ConcurrencyToken = "Timestamp";
});
project.Select("Sales.Order", settings => settings.EntitiesWithDataContracts = true);
// Build features for project, group all entities by schema into a feature
project.BuildFeatures();
// Add event handlers to before and after of scaffold
project.ScaffoldingDefinition += (source, args) =>
{
// Add code to perform operations with code builder instance before to create code file
};
project.ScaffoldedDefinition += (source, args) =>
{
// Add code to perform operations after of create code file
};
// Scaffolding =^^=
project
.ScaffoldEntityLayer()
.ScaffoldDataLayer();This package provides all definitions for CatFactory engine, this is the core for child packages.
CodeFactory: Contains objects to perform code generation.
Diagnostics: Contains objects for diagnostics.
Mapping: Contains objects for ORM.
Markup: Contains objects for markup languages.
OOP: Contains objects to modeling definitions.
This packages contains logic to import existing databases from SQL Server instances.
| Object | Supported |
|---|---|
| Tables | Yes |
| Views | Yes |
| Scalar Functions | Yes |
| Table Functions | Yes |
| Stored Procedures | Yes |
| Sequences | Not yet |
| Extended Properties | Yes |
| Data types | Yes |
This package contains code builders and definitions for .NET Core (C#).
| Object | Feature | Supported |
|---|---|---|
| Interface | Inheritance | Yes |
| Interface | Events | Yes |
| Interface | Properties | Yes |
| Interface | Methods | Yes |
| Class | Inheritance | Yes |
| Class | Events | Yes |
| Class | Fields | Yes |
| Class | Constructors | Yes |
| Class | Properties | Yes |
| Class | Methods | Yes |
| Enum | Options | Yes |
| Struct | All | Not yet |
This package provides scaffolding for Entity Framework Core.
| Category | Compatibility Chart | Supported |
|---|---|---|
| Modeling | Table splitting | Not yet |
| Modeling | Owned types | Not yet |
| Modeling | Model-level query filters | Not yet |
| Modeling | Database scalar function mapping | Not yet |
| Modeling | Self-contained type configuration for code first | Not yet |
| High Performance | DbContext pooling | Not yet |
| High Performance | Explicitly compiled queries | Not yet |
This package provides scaffolding for Asp .NET Core.
| Feature | Supported |
|---|---|
| Controllers | Yes |
| Requests | Yes |
| Responses | Yes |
| Scaffold Client | Not yet |
| Unit Tests | Not yet |
| Integration Tests | Not yet |
This package provides scaffolding for Dapper.
| Object | Supported |
|---|---|
| Tables | Yes |
| Views | Yes |
| Scalar Functions | Yes |
| Table Functions | Yes |
| Stored Procedures | Yes |
| Sequences | Yes |
This package provides scaffolding for Type Script.
| Object | Feature | Supported |
|---|---|---|
| Interface | Inheritance | Yes |
| Interface | Fields | Yes |
| Interface | Properties | Yes |
| Interface | Methods | Yes |
| Class | Inheritance | Yes |
| Class | Fields | Yes |
| Class | Constructor | Yes |
| Class | Properties | Yes |
| Class | Methods | Yes |
| Module | Methods | Yes |
In 2005 year, I was on my college days and I worked on my final project that included a lot of tables, for those days C# didn't have automatic properties also I worked on store procedures that included a lot of columns, I thought if there was a way to generate all that code because it was repetitive and I wasted time in wrote a lot of code.
In 2006 beggining I've worked for a company and I worked in a prototype to generate code but I didn't have experience and I was a junior developer, so I developed a version in WebForms that didn't allow to save the structure ha,ha,ha that project it was my first project in C# because I came from VB world but I bought a book about Web Services in DotNet and that book used C# code, that was new for me but it got me a very important idea, learn C# and I wrote all first code generation form in C#.
Later, there was a prototype of Entity for SQL, the grandfather of entity framework and I develop a simple ORM because I had table class and other classes such as Column, so after of reviewed Entity for SQL I decided to add the logic to read database and provide a simple way to read the database also of code generation.
In 2008 I built the first ORM based on my code generation engine, in that time it was called F4N1, I worked on an ORM must endure different databases engines such as SQL Server, Sybase and Oracle; so I generated a lot of classes with that engine, for that time the automated unit tests did not exist, I had a webform page that generated that code ha,ha,ha I know it was ugly and crappy but in that time that was my knowledge allowed me.
In 2011 I worked on a demo for a person that worked in his company and that person used another tool for code generation, so my code generation engine wasn't use for his work.
In 2012 I worked for a company needed to rebuilt all system with new technologies (ASP.NET MVC and Entity Framework) so I invested time about MVC and EF learning but as usual, there isn't time for that ha,ha,ha and again my code generation it wasn't considered for that upgrade =(
In 2014, I thought to make a nuget package to my code generation but in those days I didn't have the focus to accomplish that feature and always I used my code generation as a private tool, in some cases I shared my tool with some coworkers to generate code and reduce the time for code writing.
In 2016, I decided to create a nuget package and integrates with EF Core, using all experience from 10 years ago :D Please remember that from the beginning I was continuing improve the way of code generation, my first code was a crap but with the timeline I've improved the design and naming for objects.
Why I named CatFactory? It was I had a cat, her name was Mindy and that cat had manny kittens (sons), so the basic idea it was the code generation engine generates the code as fast Mindy provided kittens ha,ha,ha
- The name for this framework it was F4N1 before than CatFactory
- Framework's name is related to kitties
- Import logic uses sp_help stored procedure to retrieve the database object's definition, I learned that in my database course at college
- Load mapping for entities with MEF, it's inspired in "OdeToCode" (Scott Allen) article for Entity Framework 6.x
- Expose all settings in one class inside of project's definition is inspired on DevExpress settings for Web controls (Web Forms)
- There are three alpha versions for CatFactory as reference for Street Fighter Alpha fighting game.
- There will be two beta versions for CatFactory, the first with name Sun and second one with name Moon as reference for characters from The King of Fighters fighting game: Kusanagi Kyo and Yagami Iori.
Scaffolding Entity Framework Core with CatFactory
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent