You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This template is for a clean structured ASP.NET Core web project, follows the Clean Architecture principles, SOLID design principles, and implements the Dependency Injection, Repository, and Unit of Work design pattern, and utilizes Entity Framework Core for data access. It provides a standardized structure and organization for building robust and maintainable ASP.NET Core web applications with complete CRUD (Create, Read, Update, Delete) operations.
3
+
This template is for a clean structured ASP.NET Core API project, following the Clean Architecture principles, SOLID design principles, implementing the Dependency Injection, Repository, and Unit of Work design pattern, and utilizing Entity Framework Core for data access. It provides a standardized structure and organization for building robust and maintainable ASP.NET Core API applications with complete CRUD (Create, Read, Update, Delete) operations.
4
4
5
5
## Project Structure
6
6
@@ -10,14 +10,30 @@ The project structure is designed to promote separation of concerns and modulari
10
10
├── src
11
11
│ ├── Core # Contains the core business logic and domain models, etc.
12
12
│ ├── Infrastructure # Contains infrastructure concerns such as data access, external services, etc.
13
-
│ └── UI # Contains the user interface layer, including controllers, views, and extensions, etc.
13
+
│ └── API # Contains the API layer, including controllers, models, and extensions, etc.
14
14
├── tests
15
15
│ ├── Core.Tests # Contains unit tests for the core layer
16
16
│ ├── Infrastructure.Tests # Contains unit tests for the infrastructure layer
17
-
│ └── UI.Tests # Contains unit tests for the UI layer
17
+
│ └── API.Tests # Contains unit tests for the API layer
18
18
└── README.md # Project documentation (you are here!)
19
19
```
20
20
21
+
## REST API
22
+
23
+
The API project contains the controllers responsible for handling HTTP requests and responses, adhering to RESTful principles. Here's an overview of the key components involved in building RESTful APIs using ASP.NET Core:
24
+
25
+
1.**Controllers**: The `API` project contains controllers that handle HTTP requests and responses. Each controller is responsible for a specific resource or entity. Controllers define HTTP methods (GET, POST, PUT, DELETE) that map to specific actions for CRUD operations on entities.
26
+
27
+
2.**Models/DTOs**: The `Core` project may contain Data Transfer Objects (DTOs) that represent the data to be sent over the API. DTOs help in decoupling the client's data format from the server's data format.
28
+
29
+
3.**Routing**: The routing mechanism in ASP.NET Core maps incoming HTTP requests to the appropriate controller and action method based on the URL. RESTful APIs typically use a resource-based URL pattern.
30
+
31
+
4.**HTTP Methods**: RESTful APIs use standard HTTP methods (GET, POST, PUT, DELETE) to perform CRUD operations on resources. Each HTTP method corresponds to a specific action on the API.
32
+
33
+
5.**Status Codes**: RESTful APIs use standard HTTP status codes to indicate the success or failure of an API request. For example, 200 (OK) for successful GET requests, 201 (Created) for successful POST requests, 204 (No Content) for successful DELETE requests, etc.
34
+
35
+
6.**Validation**: RESTful APIs should include proper validation logic to ensure that incoming data is valid and adheres to the expected format.
36
+
21
37
## Getting Started
22
38
23
39
To use this project template, follow the steps below:
@@ -27,42 +43,45 @@ To use this project template, follow the steps below:
27
43
3. Open the solution in your preferred IDE (e.g., Visual Studio, Visual Studio Code).
28
44
4. Build the solution to restore NuGet packages and compile the code.
29
45
5. Configure the necessary database connection settings in the `appsettings.json` file of the Infrastructure project.
30
-
6. Open the Package Manager Console, select `Project.Infrastructure` project and run the `Update-Database` command to create the database
31
-
7. Run the application by starting the `Project.UI` project.
46
+
6. Open the Package Manager Console, select `Project.Infrastructure` project, and run the `Update-Database` command to create the database.
47
+
7. Run the application by starting the `Project.API` project.
32
48
33
49
## Project Features
34
50
35
51
This project template includes the following features:
36
52
37
53
-**Clean Architecture**: The project is structured according to the principles of Clean Architecture, which promotes separation of concerns and a clear division of responsibilities.
38
54
-**SOLID Design Principles**: The code adheres to SOLID principles (Single Responsibility, Open-Closed, Liskov Substitution, Interface Segregation, and Dependency Inversion), making it easier to maintain and extend.
39
-
-**Repository Pattern**: The repository pattern is used to abstract the data access layer and provide a consistent interface for working with data.
55
+
-**Repository Pattern**: The repository pattern abstracts the data access layer and provides a consistent interface for working with data.
40
56
-**Unit of Work Pattern**: The unit of work pattern helps manage transactions and ensures consistency when working with multiple repositories.
41
57
-**Entity Framework Core**: The project utilizes Entity Framework Core as the ORM (Object-Relational Mapping) tool for data access.
42
-
-**ASP.NET Core Web**: The project includes an ASP.NET Core web project that serves as the user interface layer, handling HTTP requests and responses.
58
+
-**ASP.NET Core API**: The project includes an ASP.NET Core API project that serves as the API layer, handling HTTP requests and responses.
43
59
-**CRUD Operations**: The project template provides a foundation for implementing complete CRUD (Create, Read, Update, Delete) operations on entities using Entity Framework Core.
44
60
-**Dependency Injection**: The project utilizes the built-in dependency injection container in ASP.NET Core, making it easy to manage and inject dependencies throughout the application.
45
-
-**Unit Testing**: The solution includes separate test projects for unit testing the core, infrastructure, and UI layers.
61
+
-**Unit Testing**: The solution includes separate test projects for unit testing the core, infrastructure, and API layers.
46
62
47
63
## Usage
48
64
49
-
The project template provides a starting point for implementing CRUD operations on entities using Entity Framework Core. You can modify and extend the existing code to suit your specific application requirements. Here's an overview of the key components involved in the CRUD operations:
65
+
The project template provides a starting point for building RESTful APIs using ASP.NET Core. You can modify and extend the existing code to suit your specific application requirements. Here's an overview of the key components involved in building RESTful APIs:
50
66
51
67
1.**Models**: The `Core` project contains the domain models representing the entities you want to perform CRUD operations on. Update the models or add new ones according to your domain.
52
68
2.**Repositories**: The `Infrastructure` project contains repository implementations that handle data access operations using Entity Framework Core. Modify the repositories or create new ones to match your entity models and database structure.
53
69
3.**Services**: The `Core` project contains services that encapsulate the business logic and orchestrate the operations on repositories. Update or create new services to handle CRUD operations on your entities.
54
-
4.**Controllers**: The `UI` project contains controllers that handle HTTP requests and responses. Update or create new controllers to expose the CRUD endpoints for your entities.
70
+
4.**Controllers**: The `API` project contains controllers that handle HTTP requests and responses. Update or create new controllers to expose the CRUD endpoints for your entities. Implement the appropriate HTTP methods (GET, POST, PUT, DELETE) and perform actions on the core services accordingly.
55
71
56
72
Make sure to update the routes, validation, and error-handling logic to align with your application requirements and best practices.
57
73
58
74
## Authors
59
75
60
76
If you have any questions or need further assistance, please contact the project author at [@kawser2133](https://www.github.com/kawser2133) || [](https://www.linkedin.com/in/kawser2133)
61
77
78
+
<ahref="https://www.buymeacoffee.com/kawser"target="_blank"><imgsrc="https://cdn.buymeacoffee.com/buttons/v2/default-yellow.png"alt="Buy Me A Coffee"style="height: 60px!important;width: 217px!important;" ></a><br/>
79
+
**Thanks for your support!**
80
+
62
81
## Contributing
63
82
64
-
I want you to know that contributions to this project are welcome. Please open an issue or submit a pull request if you have any ideas, bug fixes, or improvements.
83
+
I want you to know that contributions to this project are welcome. Please open an issue or submit a pull request if you have any ideas, bug fixes, or improvements.
65
84
66
85
## License
67
86
68
-
This project is licensed under the [MIT License](LICENSE).
87
+
This project is licensed under the [MIT License](LICENSE)."
0 commit comments