Repository navigation
Releases
EfCoreNexus.Framework 2.0.1
EfCoreNexus.Framework 2.0.1
Patch release for .NET 10 / EF Core 10, focused on CRUD correctness, tracking, concurrency, and model discovery.
This release includes several targeted bug fixes and regression tests. The public API remains unchanged.
Fixes
- NoTracking updates: Fixed updates silently losing changes when global
NoTrackingorNoTrackingWithIdentityResolutionis configured. - NoTracking deletes: Fixed ID-based deletion of entities containing owned collections with shadow keys.
- Added entities: ID-based deletion now rejects an
Addedentity before modifying its state or saving. - Concurrency: Improved detection of pending Complex-Type changes when applying expected concurrency tokens.
- Entity discovery: Respects preconfigured EF Core Complex Types.
- Inheritance: Prevents updates from copying properties between different mapped entity subtypes.
Compatibility
- No new public API or dependency upgrades.
- Existing .NET 10 / EF Core 10 requirements remain unchanged.
- Updates using incompatible mapped entity subtypes now throw an explicit exception instead of potentially modifying unrelated subtype properties.
- Advanced owned-entity and inheritance concurrency limitations are documented.
Validation
- 172 SQLite tests passed
- 7 SQL Server integration tests passed
- GitHub CI successful
- No known vulnerable dependencies reported
Installation
dotnet add package EfCoreNexus.Framework --version 2.0.1References
EfCoreNexus.Framework 2.0.0
EfCoreNexus.Framework 2.0.0
Stable v2 for .NET 10 / EF Core 10. The package ID remains
EfCoreNexus.Framework. This release provides typed async CRUD, explicit
assembly discovery, per-operation context ownership and optional multi-provider
transactions while keeping native EF APIs available.
dotnet add package EfCoreNexus.Framework --version 2.0.0Add a compatible EF Core 10 database provider separately; see
installation and setup.
Breaking changes from 1.0.5
- Runtime: .NET 10 / EF Core 10 is required. Applications on the v1 runtime
baseline must upgrade before using this package. - Setup and DI: native
DbContext,IDbContextFactory<TContext>,
IEntityTypeConfiguration<T>and concrete provider injection replace
BaseContext,BaseContextFactory,EntityTypeConfigurationDependency,
StartupConfiguration,DataAssemblyConfiguration,DataService/
IDataServiceandProviderFactory/IProviderFactory/IProvider.
Discovery uses explicit assembly boundaries. - CRUD signatures and keys: asynchronous methods with cancellation replace
the old signatures and synchronous query hooks. Create/update take the
entity's mapped key, without a separate ID argument. ID and entity delete
are distinct overloads. Native EF metadata replaces Dynamic LINQ and
attribute-only key discovery; generic CRUD requires a single CLR key. - Context and transaction ownership: ordinary calls create and asynchronously
dispose their own context.TransactionServiceand implicit shared state are
removed. Use native EF for a single save or explicitly pass the optional
TransactionRunner<TContext>context to participating writes. Borrowed writes
save the entire supplied tracker immediately. Rollback does not undo in-memory
keys or entity state; discard entities from failed workflows. - Update, delete and concurrency: updates are full scalar edits, not graph
merges or patches. Preserve original concurrency tokens; generic updates
support store-generated CLR tokens, while application-managed token renewal
requires a specialized native operation. A no-change update asserts no
version. Missing reads returnnull, missing updates throw
KeyNotFoundException, missing ID deletes are a no-op, and stale/missing
entity deletes throwDbUpdateConcurrencyException. - Sample database: the sample now uses a fresh disposable SQLite schema
with a Memo table. It does not migrate an existing SQL Server database;
production mappings, schema and data migrations remain application-owned.
See the migration guide for replacements and before/after
examples, and the API contracts before porting overrides.
Server-side authorization, tenant isolation and allowed-field validation remain
the application's responsibility; query filters and concurrency tokens are not
access checks.
The stable release preparation changes package metadata and documentation only.
It adds no framework API, implementation, dependencies, tests or release automation
to the source validated in PR #24. See the
release guide for validation and the manual release commands.