NuExt.System.Data provides a lightweight and extensible foundation for data access in .NET applications. It combines practical ADO.NET extensions, reusable DAL and database context abstractions, explicit transaction management, and provider-independent database migrations with validated history tracking.
- ADO.NET Extensions: Provides helpers for reading, converting, and manipulating data through
DataReader,DataRow, andDataTable. - DAL Infrastructure: Includes lightweight base classes and database context abstractions for implementing data access layers.
- Database Migrations: Provides provider-independent migration orchestration with ordered execution, validated migration history, optional version metadata, cancellation support, and provider-specific execution contexts.
The DAL infrastructure supports two execution models:
- Owned context: When no database context is provided, the provider-specific executor creates and owns the context. It manages the connection, transaction, commit or rollback, and resource cleanup.
- Borrowed context: When an existing database context is provided, the DAL participates in the caller's unit of work without committing, rolling back, or disposing the context.
This allows individual DAL operations to run independently while also supporting coordinated operations across multiple DAL components within the same transaction.
The migration framework is designed for application-integrated, forward-only database evolution. Migrations are registered explicitly in the order in which they must be applied, making the target schema deterministic and avoiding reflection-based discovery.
Applied migrations are stored as an ordered history. Before applying pending migrations, the framework validates that the stored history is an exact prefix of the configured migration sequence. This detects removed, renamed, reordered, or unknown migrations before any schema changes are made.
Transaction ownership is explicit and provider-controlled. A provider can execute the complete migration batch within its own transaction or participate in an existing database context, allowing migrations and application operations to share the same transaction.
System.Data.DalBase<TDbContext>: Base class for DAL implementations that supports borrowed contexts and provider-managed owned context scopes.System.Data.DataReaderExtensions: Provides extension methods for data reader operations.System.Data.DataRowExtensions: Provides extension methods for data row operations.System.Data.DataTableExtensions: Provides extension methods for data table operations.System.Data.DbMigration<TContext>: Base class for defining ordered database schema and data migrations.System.Data.DbMigrationContext: Base class for provider-specific migration execution contexts.System.Data.DbMigrator<TContext>: Validates migration configuration and applied history, and executes pending migrations.System.Data.IDbContext: Defines transaction state and lifecycle operations for database contexts.System.Data.IDbContextExecutor<TDbContext>: Defines provider-specific ownership and execution of database context scopes.System.Data.IDbMigrationExecutor<TContext>: Defines provider-specific migration execution and transaction handling.System.Data.IDbMigrationHistory<TContext>: Defines storage operations for applied migration history.
Via NuGet:
dotnet add package NuExt.System.DataOr via Visual Studio:
- Go to
Tools -> NuGet Package Manager -> Manage NuGet Packages for Solution.... - Search for
NuExt.System.Data. - Click "Install".
.NET Standard 2.0+, .NET 8/9/10 and .NET Framework 4.6.2+
For a complete provider implementation and migration example, see:
- NuExt.Minimal.Mvvm
- NuExt.Minimal.Mvvm.SourceGenerator
- NuExt.Minimal.Behaviors.Wpf
- NuExt.Minimal.Mvvm.Wpf
- NuExt.Minimal.Mvvm.MahApps.Metro
- NuExt.System
- NuExt.System.Data.SQLite
Issues and PRs are welcome. Keep changes minimal and performance-conscious.
MIT. See LICENSE.