This is my first major full-fledged project through which I learnt the Clean Architecture principles.
The project uses the complete .NET Stack from Blazor to ASP.NET Core 6.0, backed with Microsoft SQL Server. It also uses other open source components such as MudBlazor, LazyCache, AutoMapper, HangFire, MediatR
-
Normal build (This uses a normal SQL Server instance)
- Make sure you have .NET 6.0 Sdk installed in your machine.
- Open
/Quark.Server/Properties/launchSettings.json
file using any code editor. - Go the
Quark.Server
profile underprofiles
key. - Under
environmentVariables
, modify the value ofDbServer
fromlocalhost
to your own SQL Server address. If you are using LocalDB, change it to(localdb)/SQLLocalDB
. Also it is recommended to update theDbUser
andDbPassword
variables. - If you are using Visual Studio, simply start the application in
Quark.Server
launch profile. - If you are using Visual Studio code, use
dotnet run
in the terminal. - Make sure the SQL Server is properly accessible.
-
Using docker (This uses SQL Server inside docker container)
- Install Docker Desktop(For windows and macOS users) or Docker CE(For Linux users). Note that using docker in windows requires a proper installation of WSL 2.
- Download this repository zip file and extract the solution files into folder of your wish.
- Open a terminal at the that folder . Type
docker-compose up
and press enter. This command creates 2 container images, each for the ASP.NET Core app and SQL Server, after which both the containers start running. - Open your browser and browse to
https://localhost:8080
to run the web app. - Alternatively, the application can be run through Visual Studio, by choosing the Quark.Server(Kestrel) as launch profile, which runs at
https://localhost:5001
without docker. But this step requires the SQL server container to be running, which can be started from Docker desktop if not running previously. - Similarly, if using Visual Studio Code, simply use
dotnet run
in the terminal and browsehttps://localhost:5001
, while ensuring the SQL Server container is running