dataaccess_aspnetcore
A generic repository and unit-of-work framework for ASP.NET Core applications using Entity Framework Core.
What is dataaccess_aspnetcore?
DataAccess Toolbox is a framework that implements the repository and unit-of-work patterns for ASP.NET Core applications using Entity Framework Core. It provides base classes for entities and repositories, generic CRUD operations, and query helpers to streamline data access while maintaining separation of concerns.
ASP.NET Core developers building applications with Entity Framework Core who want a structured, maintainable data access layer without writing repetitive boilerplate code.
It offers a standardized, production-ready foundation for data access that reduces development time, enforces best practices, and simplifies complex query building and paging compared to manual Entity Framework implementations.
Overview
Generic repository/unit of work framework for ASP.NET Core with Entity Framework.
Use Cases
Best For
- Implementing a clean architecture with separated data access and business logic layers
- Reducing boilerplate code for common CRUD operations in ASP.NET Core APIs
- Building applications that require efficient paging and filtering of large datasets
- Standardizing data access patterns across multiple projects or teams
- Adding custom repository logic while leveraging a generic base implementation
- Controlling database schema conventions like lowercase table names or cascading deletes
Not Ideal For
- Projects not using Entity Framework Core or preferring micro-ORMs like Dapper for raw SQL control
- Rapid prototyping where minimal setup and direct Entity Framework Core usage are prioritized over architectural patterns
- Applications requiring automatic repository discovery or dynamic data access without manual registration
- Teams unwilling to depend on a vendor-specific framework with a custom NuGet feed
Pros & Cons
Pros
Generic repositories provide pre-built Get, GetAll, Add, Update, and Remove methods, significantly reducing boilerplate code for common database interactions as shown in the README examples.
Implements the unit-of-work pattern via IUnitOfWork and IUowProvider, promoting separation of concerns and making business logic more testable and maintainable.
Includes Filter, Includes, and OrderBy classes to simplify complex query construction, such as building Include chains for related entities, as demonstrated in the Query section.
Offers IDataPager for efficient retrieval of large datasets in pages, directly addressing performance concerns with large collections without custom implementation.
Cons
Requires configuring a custom NuGet feed (MyGet) and careful version management—separate branches for netcoreapp1.x vs 2.0—adding friction compared to standard EF Core setups.
The README explicitly states 'automatic discovery of repositories -- not yet', forcing developers to manually register custom repositories in the DI container.
Tightly couples applications to Digipolis's framework conventions and base classes, potentially complicating migration to other data access patterns or future .NET versions.
The unit-of-work and repository layers add extra complexity and indirection, which might be unnecessary for simple CRUD operations and could impact performance marginally.
Frequently Asked Questions
Related Projects
abpOpen-source web application framework for ASP.NET Core! Offers an opinionated architecture to build enterprise software solutions with best practices on top of the .NET. Provides the fundamental infrastructure, cross-cutting-concern implementations, startup templates, application modules, UI themes, tooling and documentation.
ASP.NET BoilerplateASP.NET Boilerplate - Web Application Framework
OrleansCloud Native application framework for .NET
fissionFast and Simple Serverless Functions for Kubernetes
Found a gem we're missing?
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.