EntityFrameworkCore.ExtensibleMigrations
0.0.1
dotnet add package EntityFrameworkCore.ExtensibleMigrations --version 0.0.1
NuGet\Install-Package EntityFrameworkCore.ExtensibleMigrations -Version 0.0.1
<PackageReference Include="EntityFrameworkCore.ExtensibleMigrations" Version="0.0.1" />
<PackageVersion Include="EntityFrameworkCore.ExtensibleMigrations" Version="0.0.1" />
<PackageReference Include="EntityFrameworkCore.ExtensibleMigrations" />
paket add EntityFrameworkCore.ExtensibleMigrations --version 0.0.1
#r "nuget: EntityFrameworkCore.ExtensibleMigrations, 0.0.1"
#:package EntityFrameworkCore.ExtensibleMigrations@0.0.1
#addin nuget:?package=EntityFrameworkCore.ExtensibleMigrations&version=0.0.1
#tool nuget:?package=EntityFrameworkCore.ExtensibleMigrations&version=0.0.1
EntityFrameworkCore.ExtensibleMigrations
An EF Core design-time extension framework for teaching the migration system about your own concepts, so they get diffed, scaffolded, and snapshotted like first-class citizens.
Why
Define custom MigrationOperation types that participate in EF Core's design-time pipeline — diffed, scaffolded, and snapshotted alongside EF's built-ins.
Examples:
- Property/class attributes that express database features EF Core doesn't natively model — e.g. a
[FullText]attribute that emits a Postgres GIN index, a[MaterializedView]annotation that emitsCREATE MATERIALIZED VIEW. - Always-on helper operations — emit
GRANTstatements when tables are created, rebuild indexes when their definition changes. - Custom codegen / snapshot output for EF's own operations.
Handlers contribute snapshot output too, so the differ sees state from the previous run and skips generating empty migrations.
Install
dotnet add package EntityFrameworkCore.ExtensibleMigrations
The package ships an MSBuild buildTransitive target that auto-wires its design-time services into your project's compile. No manual IDesignTimeServices registration is required.
Documentation
- docs/architecture.md — how the package wraps EF Core's design-time services, how
BeforeCore/AfterCorephases work, how handlers compose. - docs/handlers.md — step-by-step guide to writing your own handler trio.
- docs/snapshot-completeness.md — making framework outputs land in the EF snapshot as typed entries (Tier 1 native EF, Tier 2 consumer-side helper APIs).
- docs/examples.md — end-to-end examples with the input model and the exact migration output each produces.
- CONTRIBUTING.md — building, running tests, the integration rig + compatibility matrix.
- CHANGELOG.md.
Compatibility
- .NET 10
- EF Core 10.0.5+ (lower 10.0.x versions ship transitive packages with known CVEs that fail restore under
TreatWarningsAsErrors; see CONTRIBUTING.md for the tested matrix). - Database: provider-agnostic. Examples + integration tests target PostgreSQL via Npgsql.
Licence
MIT
| Product | Versions Compatible and additional computed target framework versions. |
|---|---|
| .NET | net10.0 is compatible. net10.0-android was computed. net10.0-browser was computed. net10.0-ios was computed. net10.0-maccatalyst was computed. net10.0-macos was computed. net10.0-tvos was computed. net10.0-windows was computed. |
-
net10.0
- Microsoft.EntityFrameworkCore (>= 10.0.7)
- Microsoft.EntityFrameworkCore.Design (>= 10.0.7)
- Microsoft.EntityFrameworkCore.Relational (>= 10.0.7)
- Microsoft.Extensions.DependencyInjection.Abstractions (>= 10.0.7)
NuGet packages
This package is not used by any NuGet packages.
GitHub repositories
This package is not used by any popular GitHub repositories.
| Version | Downloads | Last Updated |
|---|---|---|
| 0.0.1 | 41 | 5/4/2026 |