How khoa-cntt/xdwnctnn8725 works
Project Type and Purpose
• The project is a web-based shopping platform (Webshopping) built on an ASP.NET MVC (or ASP.NET Core MVC) architecture.
• Its structure—with separate areas for administration, standard controllers/views for products, brands, categories, etc.—suggests that it serves both customer-facing and admin functionalities.
• The “KLTN” in the README hints at an academic senior thesis project, so while it is a developed web application, you might want to showcase both core functionalities and extensibility areas.
File Structure for Architectural Clues
• Core Directories:
• “Controllers”: Contains controllers like HomeController, LoginController, and specialized ones such as Cart, Brand, Product, etc.
• “Views” (and nested “Views” under Admin): These folders hold the presentation components (cshtml views) that render UI for both frontend and administrative interfaces.
• “Models”: Defines the data models used throughout the application (e.g., BrandModel, CategoryModel, ProductModel, etc.).
• “Migrations”: Manages database schemas and evolution, indicating the use of Entity Framework for data access.
• “Repository”: Houses DataContext, SeedData, session extension methods, and view components (e.g., BrandsViewComponent, CategoriesViewComponent) that encapsulate business logic and data retrieval.
• “wwwroot”: Contains static resources such as CSS, JavaScript, images, and third-party libraries (Bootstrap, jQuery, etc.).
• Secondary and supporting parts:
• “Areas/Admin” for the admin-specific UI and controllers.
• Configuration files like appsettings.json which guide environment-specific settings.
• The solution and project files (.sln, .csproj) provide build and dependency management details.
• Presentation Layer:
• Application Layer:
• Business/Domain Layer:
• Data Persistence Layer:
• Controller to Models/Repository.
• Repository to Database.
• Views receive data from Controllers.