SampleDotnet.RepositoryFactory
3.1.0-preview2
dotnet add package SampleDotnet.RepositoryFactory --version 3.1.0-preview2
NuGet\Install-Package SampleDotnet.RepositoryFactory -Version 3.1.0-preview2
<PackageReference Include="SampleDotnet.RepositoryFactory" Version="3.1.0-preview2" />
paket add SampleDotnet.RepositoryFactory --version 3.1.0-preview2
#r "nuget: SampleDotnet.RepositoryFactory, 3.1.0-preview2"
// Install SampleDotnet.RepositoryFactory as a Cake Addin #addin nuget:?package=SampleDotnet.RepositoryFactory&version=3.1.0-preview2&prerelease // Install SampleDotnet.RepositoryFactory as a Cake Tool #tool nuget:?package=SampleDotnet.RepositoryFactory&version=3.1.0-preview2&prerelease
SampleDotnet.RepositoryFactory Documentation
Overview
The SampleDotnet.RepositoryFactory NuGet package provides a robust and flexible solution for managing data access using Entity Framework Core (EF Core) in .NET applications. It leverages the Repository Pattern and Unit of Work Pattern to ensure efficient database operations, transaction management, and better separation of concerns. This package simplifies working with multiple DbContext
instances and supports parallel operations using transient scoped DbContexts
managed by a DbContextFactory
.
Note: Most features in this package are currently in a preview version. While the package is stable for general use, some features may still be undergoing testing and improvements. Please provide feedback and report any issues to help us enhance the package further.
Key Features
- Repository Pattern: Provides generic repositories to manage entities with CRUD operations.
- Unit of Work Pattern: Encapsulates transaction management and ensures all operations are completed or rolled back together.
- DbContextFactory: Supports transient scoped
DbContexts
to prevent concurrency issues. - Automatic Property Management: Automatically updates
CreatedAt
andUpdatedAt
properties for entities implementingIHasDateTimeOffset
. - Flexible Service Lifetimes: Supports configuring services with various lifetimes (Scoped, Transient, Singleton) to suit different application needs.
Installation
To install the SampleDotnet.RepositoryFactory NuGet package, run the following command in the Package Manager Console:
Install-Package SampleDotnet.RepositoryFactory -Pre
Or use the .NET CLI:
dotnet add package SampleDotnet.RepositoryFactory --prerelease
Prerequisites
Ensure that your project targets one of the following frameworks: .NET 6.0, .NET 7.0, or .NET 8.0. This package does not support .NET 5.
Usage
1. Service Registration
To use the RepositoryFactory
and UnitOfWork
in your application, register the necessary services in the Startup
class or wherever you configure services in your application.
Example: Configuring Services in ASP.NET Core
public void ConfigureServices(IServiceCollection services)
{
// Add DbContextFactory for UserDbContext with the desired lifetime
services.AddDbContextFactory<UserDbContext>(options =>
{
options.UseSqlServer(Configuration.GetConnectionString("DefaultConnection"));
});
// Add repository factory with a specified service lifetime "Scoped or Transient (especially for the Consumers)"
services.AddRepositoryFactory(ServiceLifetime.Scoped);
// Additional service registrations...
}
This setup uses the traditional AddDbContextFactory
method to configure DbContextFactory
for UserDbContext
and specifies the desired service lifetime for the factory.
2. Using the Repository and Unit of Work in Controllers
After configuring the services, use the IUnitOfWork
and repository pattern in your controllers to manage database operations.
Example: UserController
public class UserController : Controller
{
private readonly IUnitOfWork _unitOfWork;
public UserController(IUnitOfWork unitOfWork)
{
_unitOfWork = unitOfWork;
}
[HttpDelete("{id}")]
public ActionResult Delete(Guid id)
{
using (var repository = _unitOfWork.CreateRepository<UserDbContext>())
{
var user = repository.FirstOrDefault<UserEntity>(u => u.Id == id);
// Perform operations on the entity...
repository.Delete(user);
// Additional operations...
}
_unitOfWork.SaveChanges();
return Ok();
}
}
3. Automatic Timestamps for Entities
If your entities implement the IHasDateTimeOffset
interface, their CreatedAt
and UpdatedAt
properties will be automatically managed when using repository methods.
Example: TestUserEntity
public class TestUserEntity : IHasDateTimeOffset
{
[Key]
[DatabaseGenerated(DatabaseGeneratedOption.Identity)]
public Guid Id { get; set; }
public string Name { get; set; }
public string Surname { get; set; }
public DateTimeOffset? CreatedAt { get; set; }
public DateTimeOffset? UpdatedAt { get; set; }
}
4. Parallel Operations and DbContextFactory
The package supports parallel operations by using a DbContextFactory
to create new DbContext
instances. This approach prevents concurrency issues that occur when the same DbContext
instance is used across multiple threads.
Special Note on Transaction Management
IMPORTANT: Proper transaction management is crucial when working with multiple
DbContext
instances.
Key Points to Consider:
Using Multiple DbContexts: If you are using multiple
DbContext
instances, each managing its own transaction, be aware that if a transaction commits successfully on oneDbContext
but fails on another, you may need to manually roll back already committed transactions to maintain data consistency. This scenario requires careful handling to ensure that all related changes are either fully committed or completely rolled back across all DbContexts.Using a Single DbContext: When using a single
DbContext
instance for all operations within a unit of work, transaction management is simplified. All operations are either committed together or rolled back together, eliminating the need to manually roll back already committed transactions from differentDbContext
instances.
Best Practice: To avoid the complexity of handling multiple transactions, use a single DbContext
instance within the scope of a unit of work whenever possible. This approach ensures straightforward transaction management and helps maintain data integrity.
Descriptions of Key Components
IUnitOfWork Interface
The IUnitOfWork
interface defines methods for managing database transactions and repositories:
CreateRepository<TDbContext>()
: Creates a new repository for the specifiedDbContext
.SaveChanges()
: Commits all pending changes to the database.SaveChangesAsync()
: Asynchronously commits all pending changes to the database.IsDbConcurrencyExceptionThrown
: Indicates if a concurrency exception occurred.SaveChangesException
: Provides details about any exception thrown during the save operation.
Repository<TDbContext> Class
A generic repository class that provides CRUD operations and additional methods for querying and manipulating entities:
AsQueryable<T>()
: Returns anIQueryable
for the specified entity type.Delete<T>()
: Deletes an entity.Find<T>()
andFindAsync<T>()
: Finds entities by primary key values.Insert<T>()
andInsertAsync<T>()
: Inserts new entities.Update<T>()
: Updates entities.
DbContextFactory and Service Lifetimes
The DbContextFactory
can now be configured with different lifetimes (Scoped, Transient, Singleton) based on your application's needs. Using a transient lifetime is particularly useful for avoiding concurrency issues in multi-threaded environments.
Transaction Management
The UnitOfWork
and TransactionManager
handle transaction management, ensuring that all operations within a unit of work are either committed or rolled back together.
Best Practices
- Use Scoped or Transient Services: Use scoped or transient services for the
UnitOfWork
and related services depending on your application's concurrency requirements. - Avoid Long-Running Operations: Keep the
DbContext
lifespan short to avoid holding resources longer than necessary. - Handle Exceptions Gracefully: Use
IsDbConcurrencyExceptionThrown
andSaveChangesException
to handle concurrency and other exceptions effectively.
Conclusion
The SampleDotnet.RepositoryFactory NuGet package provides a streamlined way to manage data access in .NET applications, leveraging best practices for transaction management and parallel operations. With support for various service lifetimes, you can now tailor the package to suit your application's specific needs. By following this guide, you can easily integrate this package into your projects and take advantage of its robust features.
For more details or support, please refer to the package documentation or reach out to the community for assistance.
Product | Versions Compatible and additional computed target framework versions. |
---|---|
.NET | net6.0 is compatible. net6.0-android was computed. net6.0-ios was computed. net6.0-maccatalyst was computed. net6.0-macos was computed. net6.0-tvos was computed. net6.0-windows was computed. net7.0 is compatible. net7.0-android was computed. net7.0-ios was computed. net7.0-maccatalyst was computed. net7.0-macos was computed. net7.0-tvos was computed. net7.0-windows was computed. net8.0 is compatible. net8.0-android was computed. net8.0-browser was computed. net8.0-ios was computed. net8.0-maccatalyst was computed. net8.0-macos was computed. net8.0-tvos was computed. net8.0-windows was computed. |
-
net6.0
- AutoMapper.Extensions.Microsoft.DependencyInjection (>= 12.0.1)
- Microsoft.AspNetCore.Mvc.NewtonsoftJson (> 6.0.0)
- Microsoft.Data.SqlClient (>= 6.0.0-preview1.24240.8)
- Microsoft.EntityFrameworkCore (> 6.0.0)
- Microsoft.EntityFrameworkCore.Relational (> 6.0.0)
- Microsoft.EntityFrameworkCore.SqlServer (> 6.0.0)
-
net7.0
- AutoMapper.Extensions.Microsoft.DependencyInjection (>= 12.0.1)
- Microsoft.AspNetCore.Mvc.NewtonsoftJson (> 7.0.0)
- Microsoft.Data.SqlClient (>= 6.0.0-preview1.24240.8)
- Microsoft.EntityFrameworkCore (> 7.0.0)
- Microsoft.EntityFrameworkCore.Relational (> 7.0.0)
- Microsoft.EntityFrameworkCore.SqlServer (> 7.0.0)
-
net8.0
- AutoMapper.Extensions.Microsoft.DependencyInjection (>= 12.0.1)
- Microsoft.AspNetCore.Mvc.NewtonsoftJson (> 8.0.0)
- Microsoft.Data.SqlClient (>= 6.0.0-preview1.24240.8)
- Microsoft.EntityFrameworkCore (> 8.0.0)
- Microsoft.EntityFrameworkCore.Relational (> 8.0.0)
- Microsoft.EntityFrameworkCore.SqlServer (> 8.0.0)
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 | |
---|---|---|---|
3.1.0-preview2 | 52 | 9/3/2024 | |
3.0.3-preview1 | 87 | 9/1/2024 | |
3.0.1 | 300 | 4/9/2023 | |
3.0.0.5-alpha | 181 | 4/8/2023 | |
2.1.0 | 271 | 3/18/2023 | |
2.0.0 | 277 | 3/13/2023 | |
1.0.0 | 287 | 2/25/2023 |