Skip to content
Clean Architecture Solution Template for Angular 9 and .NET Core 3.1
C# TypeScript HTML Other
Branch: master
Clone or download

Latest commit

jasontaylordev Merge pull request #97 from engineers-tools/patch-1
Fixed example Migration line in 'README.md'
Latest commit bd88f17 Apr 1, 2020

Files

Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.github Update dotnetcore.yml Mar 26, 2020
src Update type for not found problem details. Mar 31, 2020
tests Stop nesting handlers within queries / commands. Mar 23, 2020
.gitignore Updated Mar 30, 2020
CODE_OF_CONDUCT.md Create CODE_OF_CONDUCT.md Oct 10, 2019
CleanArchitecture.sln fix path \Src->\src Dec 8, 2019
LICENSE Initial commit Oct 7, 2019
README.md Merge branch 'master' into patch-1 Apr 1, 2020

README.md

Clean Architecture Solution Template

.NET Core Build status Clean.Architecture.Solution.Template NuGet Package Twitter Follow


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).

Technologies

  • .NET Core 3.1
  • ASP .NET Core 3.1
  • Entity Framework Core 3.1
  • Angular 9

Getting Started

The easiest way to get started is to install the NuGet package and run dotnet new ca-sln:

  1. Install the latest .NET Core SDK
  2. Install the latest Node.js LTS
  3. Run dotnet new --install Clean.Architecture.Solution.Template to install the project template
  4. Create a folder for your solution and cd into it (the template will use it as project name)
  5. Run dotnet new ca-sln to create a new project
  6. Navigate to src/WebUI and run dotnet run to launch the project

Check out my blog post for more information.

Database Configuration

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 prefer to use SQL Server, you will need to update Infrastructure/DependencyInjection.cs. Change from:

#if DEBUG
    services.AddDbContext<ApplicationDbContext>(options =>
        options.UseInMemoryDatabase("CleanArchitectureDb"));
#else
    services.AddDbContext<ApplicationDbContext>(options =>
        options.UseSqlServer(
            configuration.GetConnectionString("DefaultConnection"),
            b => b.MigrationsAssembly(typeof(ApplicationDbContext).Assembly.FullName)));
#endif 

Change to:

services.AddDbContext<ApplicationDbContext>(options =>
    options.UseSqlServer(
        configuration.GetConnectionString("DefaultConnection"),
        b => b.MigrationsAssembly(typeof(ApplicationDbContext).Assembly.FullName)));

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.

Database Migrations

To use 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)
  • --startup-project src/WebUI
  • --output-dir Persistence/Migrations

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

Overview

Domain

This will contain all entities, enums, exceptions, interfaces, types and logic specific to the domain layer.

Application

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.

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.

WebUI

This layer is a single page application based on Angular 8 and ASP.NET Core 3. 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.

Support

If you are having problems, please let us know by raising a new issue.

License

This project is licensed with the MIT license.

You can’t perform that action at this time.