// the find
ErikEJ/EFCorePowerTools
Entity Framework Core Power Tools - reverse engineering, migrations and model visualization in Visual Studio & CLI
EF Core Power Tools is a Visual Studio extension and cross-platform CLI (efcpt) that reverse-engineers existing databases into EF Core model classes, scaffolds stored procedures and TVFs into typed C# wrappers, and renders your DbContext as a DGML or Mermaid ER diagram. It fills gaps that the built-in `dotnet ef dbcontext scaffold` leaves wide open, particularly around stored procedures and visualization. Target audience is teams inheriting an existing database schema who don't want to hand-write 200 entity classes.
T4 template overrides for generated code — you put your templates in EFCore/ and they win, no partial class hacks needed. Stored procedure scaffolding into typed result-set classes is genuinely useful and something the official tooling just doesn't do. The efcpt CLI with an efcpt-config.json config file makes the workflow reproducible and CI-friendly without requiring Visual Studio. DACPAC as a reverse-engineering source is a real differentiator for SQL Server Data Tools shops — scaffold from a .dacpac without needing a live connection.
The multi-version assembly split (RevEng.Core.80, .90, .100) means bugs often need to be fixed in three places; it's structural tech debt that will slow down maintenance as EF Core keeps shipping. PostgreSQL support is a second-class citizen — stored procedure scaffolding works but the advanced SQL Server features (DACPAC, some routine types) are simply absent. Generated mappings for complex schemas with many-to-many join tables and owned entities frequently need manual cleanup; the tool doesn't warn you, so you find out when something breaks at runtime. The Visual Studio extension and the CLI tool are separate install paths with partially overlapping feature sets, which makes it non-obvious which one to trust when they disagree.