Net.WebApi.Template
1.0.0-rc.6
dotnet new install Net.WebApi.Template::1.0.0-rc.6
<img align="left" width="116" height="116" src="https://raw.githubusercontent.com/marlonajgayle/dotnet-web-api-template/develop/src/content/.template.config/icon.png" />
dotnet Web API Solution Template
A modern multi-project.NET project template that implements a maintainable enterprise-level API application with Api versioning, Fluent email, Fluent validation, JWT authentication, Identity role-based authorization, InMemory caching, IP rate limiting, CQRS with Mediator, Sirilog, and Swagger using Domain Driven Design (DDD) and architecture princliples.
Table of Contents
Prerequisites
You will need the following tools:
- Visual Studio Code or Visual Studio 2022 (version 17.5.0 or later)
- .NET Core SDK 8.0
- Docker Desktop
Architecture Overview
This is a multi-project solution that utilizes Domain Driven Design (DDD) and CQRS patterns to create a maintainable web API application using .NET 8 that allows it to run on Linux or Windows and in Docker environments.
Figure.1 Application structure
Instructions
Installation:
- Install the latest .NET Core 8 SDK.
- Run
dotnet new --install Net.WebApi.Template::1.0.0-rc.6
to install the project template
C:\> dotnet new install Net.WebApi.Template::1.0.0-rc.6
The following template packages will be installed:
Net.WebApi.Template::1.0.0-rc.6
Success: Net.WebApi.Template::1.0.0-rc.6 installed the following templates:
Template Name Short Name Language Tags
------------------------------ ---------- -------- ------------------------
.NET Web API Solution Template netwebapi [C#] WebAPI/Cloud/Service/Web
Using Visual Studio Code w/ Docker
Ensure you have installed and configured docker in your environment as this will be required to run the containers. After installing .NET Web API Solution Template(Net.WebApi.Template::1.0.0-rc.6) Launch Visual Studio Code and create your project folder. Open the VS Code terminal window and execute the following command to create your application:
dotnet new netwebapi --name MyProject
Create initial database migration
- Nagigate into the project folder
cd MyProject
. - Install
dotnet ef
as a global tool with the following command:
dotnet tool install --global dotnet-ef
You can invoke the tool using the following command: dotnet-ef
Tool 'dotnet-ef' (version '8.0.4') was successfully installed.
- Next create initial database migration with the following command:
dotnet ef migrations add InitialCreate --context <ProjectNameDbContext>\
--startup-project src/ProjectName.Api/ProjectName.Api.csproj\
--project src/ProjectName.Persistence/ProjectName.Persistence.csproj
Build started...
Build succeeded.
Development
Server=(localdb)\MSSQLLocalDB;Database=application_db;Trusted_Connection=True;MultipleActiveResultSets=true
Done. To undo this action, use 'ef migrations remove'
PS C:\rojects\MyProject>
By default, the project applies database migrations on startup. If you want disable this behaviour, you can set appsettings.Local.json
{
"UseDatabaseInitializer": true
}
Launch project with Docker
Web API uses HTTPS and relies on certificates for trust, identiy and encryption. To run the template project using Docker over HTTPS during development do the following:
- Generate certificate using 'dotnet dev-certs' (for localhost only!):
Note Update docker-compose file with dev-cert password used.
On Windows using Linux containers
dotnet dev-certs https -ep "$env:USERPROFILE\.aspnet\https\aspnetapp.pfx" -p your_password
dotnet dev-certs https --trust
Note
When using PowerShell, replace %USERPROFILE%
with $env:USERPROFILE
.
On macOS or Linux
dotnet dev-certs https -ep "${HOME}\.aspnet\https\aspnetapp.pfx" -p your_password
dotnet dev-certs https --trust
To launch the application immediately execute the Docker compose commands from the root of your project:
docker-compose up --build
While building the docker images, you should see something like the following image, and the process should take between 1 and 3 minutes to complete, depending on your systems speed.
[+] Building 8.2s (26/26) FINISHED
=> [internal] load build definition from Dockerfile 0.0s
=> => transferring dockerfile: 32B 0.0s
=> [internal] load .dockerignore 0.0s
=> => transferring context: 2B 0.0s
=> [internal] load metadata for mcr.microsoft.com/dotnet/aspnet:7.0-alpine 0.4s
=> [internal] load metadata for mcr.microsoft.com/dotnet/sdk:7.0 0.3s
=> [stage-1 1/4] FROM mcr.microsoft.com/dotnet/aspnet:7.0-alpine@sha256:be84475ff03cf6e2c11e9f730abd27cae6ae6dcdb9fd8dbebf9b787509ee6b4d 0.0s
=> [internal] load build context 0.2s
=> => transferring context: 138.91kB 0.1s
=> [build-env 1/16] FROM mcr.microsoft.com/dotnet/sdk:7.0@sha256:f712881bafadf0e56250ece1da28ba2baedd03fb3dd49a67f209f9d0cf928e81 0.0s
=> CACHED [build-env 2/16] WORKDIR /app 0.0s
=> CACHED [build-env 3/16] COPY *.sln . 0.0s
=> CACHED [build-env 4/16] COPY src/NetWebApiTemplate.Api/*.csproj ./src/NetWebApiTemplate.Api/ 0.0s
=> CACHED [build-env 5/16] COPY src/NetWebApiTemplate.Domain/*.csproj ./src/NetWebApiTemplate.Domain/ 0.0s
=> CACHED [build-env 6/16] COPY src/NetWebApiTemplate.Application/*.csproj ./src/NetWebApiTemplate.Application/ 0.0s
=> CACHED [build-env 7/16] COPY src/NetWebApiTemplate.Infrastructure/*.csproj ./src/NetWebApiTemplate.Infrastructure/ 0.0s
=> CACHED [build-env 8/16] COPY src/NetWebApiTemplate.Persistence/*.csproj ./src/NetWebApiTemplate.Persistence/ 0.0s
=> CACHED [build-env 9/16] RUN dotnet restore 0.0s
=> [build-env 10/16] COPY src/NetWebApiTemplate.Api/. ./src/NetWebApiTemplate.Api/ 0.1s
=> [build-env 11/16] COPY src/NetWebApiTemplate.Domain/. ./src/NetWebApiTemplate.Domain/ 0.0s
=> [build-env 12/16] COPY src/NetWebApiTemplate.Application/. ./src/NetWebApiTemplate.Application/ 0.1s
=> [build-env 13/16] COPY src/NetWebApiTemplate.Infrastructure/. ./src/NetWebApiTemplate.Infrastructure/ 0.1s
=> [build-env 14/16] COPY src/NetWebApiTemplate.Persistence/. ./src/NetWebApiTemplate.Persistence/ 0.0s
=> [build-env 15/16] WORKDIR /app/src/NetWebApiTemplate.Api 0.0s
=> [build-env 16/16] RUN dotnet publish -c Release -o out 7.1s
=> CACHED [stage-1 2/4] RUN apk add --no-cache icu-libs krb5-libs libgcc libintl libssl1.1 libstdc++ zlib 0.0s
=> CACHED [stage-1 3/4] WORKDIR /app 0.0s
=> CACHED [stage-1 4/4] COPY --from=build-env /app/src/NetWebApiTemplate.Api/out ./ 0.0s
=> exporting to image 0.0s
=> => exporting layers 0.0s
=> => writing image sha256:c03a3d62fdb58e63dbdc63d1e39d4b5d435bdc0b3d70c575f990019316a5ff07 0.0s
=> => naming to docker.io/library/NetWebApiTemplate-webapi
You should be able to browse to the application by using the below URL :
Swagger : https://localhost:44372/swagger
Health : https://localhost:44372/health
Using Visual Studio:
Ensure Visual Studio 2022 (version 17.5.0 or later) is installed. Launch Visual Studio 2022 and Select WebAPI from the project type drop down. Select the .NET Web API Solution template you want to install and follow the instructions.
Database Setup
To setup the SQL Server database following the instructions below:
- Reveiw the connection string in appsettings.Development.json and update the database name.
- Run
dotnet ef migrations add Initial --context <ProjectName>DbContext
to add migation with EF Core - Run
dotnet ef database update Initial
to create application database.
Third Party Libraries
- AspNetCoreRateLimit
- Dapper
- Fluent Email
- Fluent Validation
- HashidsCore.NET
- Mediator.SourceGenerator
- Polly
- Serilog
Contributions
Credits
Icon made by DinosoftLabs from www.flaticon.com
Versions
The main branch is running .NET 8.0
License
This project is licensed under the MIT License - see the LICENSE.md main branch is running .NET 8.0 file for details.
This package has no dependencies.
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 |
---|---|---|
1.0.0-rc.6 | 59 | 9/23/2024 |
1.0.0-rc.5 | 294 | 4/22/2023 |
1.0.0-rc.4 | 84 | 4/22/2023 |
1.0.0-rc.3 | 87 | 4/21/2023 |
1.0.0-rc.2 | 88 | 4/21/2023 |
1.0.0-rc.1 | 96 | 4/12/2023 |
1.0.0-betta.12 | 96 | 4/4/2023 |
1.0.0-beta.16 | 85 | 4/8/2023 |
1.0.0-beta.11 | 93 | 4/4/2023 |
1.0.0-beta.10 | 93 | 4/4/2023 |
1.0.0-beta.8 | 79 | 4/4/2023 |
1.0.0-beta.6 | 92 | 4/3/2023 |
1.0.0-beta.5 | 89 | 3/26/2023 |
1.0.0-beta.4 | 99 | 3/12/2023 |
1.0.0-beta.3 | 91 | 2/12/2023 |