EugenioBandeira.CleanArchTemplate 1.1.5

EugenioBandeira.CleanArchTemplate

.NET 10 dotnet new template for building production-ready Web APIs with Clean Architecture and .NET Aspire.

Prerequisites

• .NET 10 SDK
• .NET Aspire workload:

dotnet workload install aspire

Installation

dotnet new install EugenioBandeira.CleanArchTemplate

Usage

dotnet new clean-arch -n MyProject

What You Get

Generated Structure

MyProject/
├── 01 - aspire/
│   ├── 01 - AppHost/          # Aspire orchestration host
│   └── 02 - ServiceDefaults/  # Shared OTEL, health checks, service discovery
├── 02 - src/
│   ├── 01 - Api/              # Endpoints, middlewares, extensions
│   ├── 02 - Application/      # Handlers, validators, mappers
│   ├── 03 - Domain/           # Entities, interfaces, constants
│   ├── 04 - IoC/              # Dependency injection wiring
│   └── 05 - Infrastructure/   # Repository implementations
├── 03 - tests/
│   ├── 01 - Common/           # Shared test builders
│   ├── 02 - Validators/       # FluentValidation tests
│   ├── 03 - Handlers/         # Handler unit tests
│   ├── 04 - Repositories/     # Repository tests
│   └── 05 - Integration/      # API integration tests
├── docs/                      # Architecture docs and ADRs
├── iac/                       # Infrastructure as Code
├── k8s/                       # Kubernetes manifests
└── Dockerfile

Post-Generation Setup

1. Update ConnectionStrings.DefaultConnection in appsettings.json
2. Implement ExampleRepository.cs with your chosen persistence technology
3. Register the repository in InfrastructureDependencyInjection.cs
4. Update Cors.AllowedOrigins with your frontend URL
5. Update OpenApi contact info in appsettings.json
6. Set OTEL_EXPORTER_OTLP_ENDPOINT to enable observability export (optional)
7. Replace the Example* stubs with your own features

Full documentation, architecture details, middleware descriptions, and the step-by-step guide for adding new features are in the generated project's README.md.

Contributing

1. Fork and branch from master:

git checkout -b feat/your-feature

2. Make changes inside templates/clean-arch/
3. Verify the template builds:

dotnet build templates/clean-arch/CleanArch.slnx -c Release

Running dotnet build once also configures the pre-commit git hook automatically via Directory.Build.props. From that point on, commits that break the build are blocked locally.

4. Commit using Conventional Commits and open a PR targeting master
5. After merging, the release workflow automatically bumps PackageVersion and publishes to NuGet:
   • fix:, refactor:, chore: → patch bump
   • feat: → minor bump
   • feat!: / BREAKING CHANGE → major bump

License

MIT © eugeniobandeira