Clean Architecture Solution Template
This is a solution template for creating a Single Page App (SPA) with Angular and ASP.NET Core following the principles of Clean Architecture. Create a new project based on this template by clicking the above Use this template button or by installing and running the associated NuGet package (see Getting Started for full details).
- .NET Core 3.1
- ASP .NET Core 3.1
- Entity Framework Core 3.1
- Angular 9
- NUnit, FluentAssertions, Moq & Respawn
The easiest way to get started is to install the NuGet package and run
dotnet new ca-sln:
- Install the latest .NET Core SDK
- Install the latest Node.js LTS
dotnet new --install Clean.Architecture.Solution.Templateto install the project template
- Create a folder for your solution and cd into it (the template will use it as project name)
dotnet new ca-slnto create a new project
- Navigate to
dotnet runto launch the project
Check out my blog post for more information.
The template is configured to use an in-memory database by default. This ensures that all users will be able to run the solution without needing to set up additional infrastructure (e.g. SQL Server).
If you would like to use SQL Server, you will need to update WebUI/appsettings.json as follows:
Verify that the DefaultConnection connection string within appsettings.json points to a valid SQL Server instance.
When you run the application the database will be automatically created (if necessary) and the latest migrations will be applied.
dotnet-ef for your migrations please add the following flags to your command (values assume you are executing from repository root)
--project src/Infrastructure(optional if in this folder)
For example, to add a new migration from the root folder:
dotnet ef migrations add "SampleMigration" --project src\Infrastructure --startup-project src\WebUI --output-dir Persistence\Migrations
This will contain all entities, enums, exceptions, interfaces, types and logic specific to the domain layer.
This layer contains all application logic. It is dependent on the domain layer, but has no dependencies on any other layer or project. This layer defines interfaces that are implemented by outside layers. For example, if the application need to access a notification service, a new interface would be added to application and an implementation would be created within infrastructure.
This layer contains classes for accessing external resources such as file systems, web services, smtp, and so on. These classes should be based on interfaces defined within the application layer.
This layer is a single page application based on Angular 9 and ASP.NET Core 3.1. This layer depends on both the Application and Infrastructure layers, however, the dependency on Infrastructure is only to support dependency injection. Therefore only Startup.cs should reference Infrastructure.
If you are having problems, please let us know by raising a new issue.
This project is licensed with the MIT license.