EF Core Power Tools

Reverse engineering, model visualization and migrations UI for EF Core. For Visual Studio 2019 and 2022.

Aims to lower the bar for getting started with EF Core, by providing GUI based assistance with reverse engineering of an existing database, creating migrations and visualizing your DbContext model.

Demo video - Introduction

Demo video - Advanced features

EF Core Power Tools presentation

My tools and utilities for embedded database development

The tool and GitHub based support is free, but I would be very grateful for a rating or review here, and I also appreciate sponsorships

Documentation

Reverse Engineering Quick Start

User guide

Release notes

Downloads/builds

Requirements

.NET Framework 4.7.2 or later is required. For EF Core reverse engineering, .NET Core 3.1 x64 runtime must be installed.

Release

Download the latest version of the Visual Studio extension from Visual Studio MarketPlace

Or just install from the Extensions dialog in Visual Studio.

Daily build

You can download the daily build from Open VSIX Gallery

Ensure you always have the latest daily build (if you are brave) by installing this extension

Related NuGet packages

ErikEJ.EntityFrameworkCore.DgmlBuilder

Adds the AsDgml() extension method to any derived DbContext. The method will create a DGML graph of your DbContext Model, that you can then view in the Visual Studio DGML viewer

ErikEJ.EntityFrameworkCore.SqlServer.Dacpac

Reverse engineer a SQL Server .dacpac with the EF Core tooling

ErikEJ.EntityFrameworkCore.SqlServer.SqlQuery

Materialize abritary classes and scalar values from EF Core using raw SQL

How do I contribute

If you encounter a bug or have a feature request, please use the Issue Tracker. The project is also open for pull requests following standard pull request guidelines

Building and debugging

To build and debug, run latest version of Visual Studio as Administrator with the "Visual Studio extension development workload" installed. Make EFCorePowerTools the startup project, and ensure your build configuration is Debug, AnyCPU.

Smoke testing changes to reverse engineering

You can smoke test changes to reverse engineering. Launch one of the efreveng console apps in the debugger using the name of a file in the TestFiles folder as parameter.

In the ScaffoldingTester solution there are scripts to populate Northwind and Chinook databases with the required objects.