MehrdadShirvani/ASP.NET
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

refactor: rename project based session00

Browse Source
This commit is contained in:
MehrdadShirvani
2025-07-18 11:20:49 +03:30
parent 8177394e06
commit baacd43252
1 changed files with 5 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files
ProjectOrientedSessions/Session00/Project Structure.md → ProjectOrientedSessions/Session00/Session00 Architecture.md
+5 -12
View File
@@ -1,4 +1,4 @@
# Overview of Clean Architecture in an ASP.NET Core Project (by Chat GPT) # Overview of Clean Architecture
Clean Architecture is a software design pattern that promotes separation of concerns, testability, and maintainability. It structures an application into layers, ensuring dependencies flow inwards (towards business logic) and that the core logic is independent of frameworks and external dependencies. Clean Architecture is a software design pattern that promotes separation of concerns, testability, and maintainability. It structures an application into layers, ensuring dependencies flow inwards (towards business logic) and that the core logic is independent of frameworks and external dependencies.
@@ -186,15 +186,8 @@ This ensures the **business logic is central** and **not coupled** to frameworks
--- ---
### **Summary**
- **Domain Layer**: Core business logic (Entities, Domain Events, Domain Services).
- **Application Layer**: Use cases (Application Services, CQRS, DTOs).
- **Infrastructure Layer**: External dependencies (Repositories, External APIs, Logging).
- **Presentation Layer**: UI & API (Controllers, Views, Frontend).
# Backend Project Structure # Backend Project Structure
## **Solution Name: MyApp (or your project name)** ## **Solution Name: MyApp**
📂 **MyApp.sln** (Solution file) 📂 **MyApp.sln** (Solution file)
@@ -244,14 +237,12 @@ This ensures the **business logic is central** and **not coupled** to frameworks
- **Purpose:** Represents the core business logic and entities without dependencies on infrastructure or frameworks. - **Purpose:** Represents the core business logic and entities without dependencies on infrastructure or frameworks.
📂 `MyApp.Domain` 📂 `MyApp.Domain`
- 📂 **Aggregates** – Groups related entities following DDD principles. - 📂 **Aggregates** – Groups related entities following DDD principles.
- 📂 **Framework** - **Interfaces** – Contains domain-level abstractions like repository interfaces and entity interface. - 📂 **Framework** - **Interfaces** – Contains domain-level abstractions like repository interfaces and entity interface.
- 📂 **Framework** - **Interfaces** – **Repositories** - 📂 **Framework** - **Interfaces** – **Repositories**
- 📂 **Framework** - **Base** - 📂 **Framework** - **Base**
- 📂 **Enums** – Defines domain-specific enumerations. - 📂 **Enums** – Defines domain-specific enumerations.
- 📂 **Factories** - 📂 **Factories**
### Dependencies: ### Dependencies:
- Packages: - Packages:
- Microsoft.Extensions.DependencyInjection - Microsoft.Extensions.DependencyInjection
@@ -262,7 +253,6 @@ This ensures the **business logic is central** and **not coupled** to frameworks
- **Purpose:** Implements external dependencies such as databases, logging, APIs, and caching. - **Purpose:** Implements external dependencies such as databases, logging, APIs, and caching.
📂 `MyApp.Infrastructure` 📂 `MyApp.Infrastructure`
- 📂 **Framework** - **Base** – Implements `IRepository<TEntity>` for data access. - 📂 **Framework** - **Base** – Implements `IRepository<TEntity>` for data access.
- 📂 **Configurations** – Stores EF Core entity configurations. - 📂 **Configurations** – Stores EF Core entity configurations.
- 📂 **Services** - Repositories - 📂 **Services** - Repositories
@@ -284,4 +274,7 @@ This ensures the **business logic is central** and **not coupled** to frameworks
- 📂 `MyApp.Tests` – Unit and integration tests. - 📂 `MyApp.Tests` – Unit and integration tests.
- 📂 `MyApp.Shared` – Shared utilities (cross-cutting concerns like constants, helpers). - 📂 `MyApp.Shared` – Shared utilities (cross-cutting concerns like constants, helpers).
# Acknowledgements
- ChatGPT for snippet refinement and explanations