# CleanArchitecture-VueJS **Repository Path**: called-brother/CleanArchitecture-VueJS ## Basic Information - **Project Name**: CleanArchitecture-VueJS - **Description**: No description available - **Primary Language**: Unknown - **License**: MIT - **Default Branch**: main - **Homepage**: None - **GVP Project**: No ## Statistics - **Stars**: 0 - **Forks**: 0 - **Created**: 2025-01-04 - **Last Updated**: 2025-01-04 ## Categories & Tags **Categories**: Uncategorized **Tags**: None ## README # Clean Architecture with VueJS v2.6 ## Technologies * [ASP.NET Core 6](https://docs.microsoft.com/en-us/aspnet/core/introduction-to-aspnet-core?view=aspnetcore-6.0) * [Entity Framework Core 6](https://docs.microsoft.com/en-us/ef/core/) * [VueJS 2.6](https://vuejs.org/) * [MediatR](https://github.com/jbogard/MediatR) * [AutoMapper](https://automapper.org/) * [FluentValidation](https://fluentvalidation.net/) * [xUnit](https://xunit.net/), [FluentAssertions](https://fluentassertions.com/) & [Moq](https://github.com/moq) ## Getting Started 1. Install the latest [.NET 5 SDK](https://dotnet.microsoft.com/download/dotnet/5.0) 2. Install the latest [Node.js LTS](https://nodejs.org/en/) 3. Navigate to `WebUI/ClientApp` and run `npm install` 4. Navigate to `WebUI/ClientApp` and run `npm run serve` to launch the front end (VueJS) 5. Navigate to `WebUI` and run `dotnet run` to launch the back end (ASP.NET Core Web API) ### 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 like to use SQL Server, you will need to update **WebUI/appsettings.json** as follows: ```json "UseInMemoryDatabase": false, ``` 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 Infrastructure` (optional if in this folder) * `--startup-project WebUI` * `--output-dir Persistence/Migrations` For example, to add a new migration from the root folder: `dotnet ef migrations add "SampleMigration" --project Infrastructure --startup-project 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 VueJS 2.6 and ASP.NET Core 5. 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. ## License This project is licensed with the [MIT license](LICENSE).