create-repository

To generate repository implementations using EF Core, you create a class named {Entity}Repository implementing I{Entity}Repository in the Infrastructure layer. This scaffolds read, add, update, and delete data operations while enforcing that repositories perform only data operations.

Yes, Dapper is supported as an alternative backend for Domain repository pattern scaffolding. You can generate repository implementations for Domain interfaces using Dapper in the Infrastructure layer, covering read, add, update, and delete data operations.

When generating repositories for Domain-Driven Design, UnitOfWork handles transaction delegation. The generated repository implementations enforce a strict separation where repositories perform only data operations and rely on UnitOfWork for transaction management.

Yes, the generated repository scaffolding supports both read and write data operations. It produces scaffolding for read/write data access patterns, specifically covering read, add, update, and delete operations aligned with the Repository pattern.

You need to generate repository implementations for the Infrastructure layer when adopting the Repository pattern in Domain-Driven Design. It applies to projects requiring data access scaffolding that separates data operations from transaction management.

The repository pattern delegates transactions to UnitOfWork to enforce a strict separation of concerns. Repositories perform only data operations like read, add, update, and delete, while UnitOfWork manages transaction boundaries in the Infrastructure layer.