How deboraj-roy/asp.net-core-mvc-net-8 works
Main Components
• Frontend/Web UI: Represented by the BulkyWeb project. It contains the MVC controllers, Views (separated by Areas such as Admin, Customer, and Identity), view components (e.g., the ShoppingCartViewComponent), static assets (CSS, JavaScript, images in wwwroot), and configuration (appsettings and Program.cs).
• Backend/Data Access Layer: Shown by the Bulky.DataAccess project. It includes the Entity Framework Core DbContext (ApplicationDbContext.cs), migrations, repository implementations (Repository and UnitOfWork patterns), and initializing the database (DbInitializer).
• Domain/Models: The Bulky.Models folder contains all the core domain objects (e.g., Product, Category, Company, ShoppingCart, OrderHeader, etc.) and view models that represent the data structure for views.
• Utility/Supporting Services: The Bulky.Utility project holds utilities such as EmailSender, StripeSettings (for payment integrations), and a static definitions class (SD.cs).
Establish Relationships and Data Flow
• The Web UI (BulkyWeb) interacts with the Domain Models to process user input and display data. Controllers (in Admin and Customer areas) serve as the entry point for user requests.
• Data flow from the Web UI is routed to the Data Access layer. Repositories (e.g., ProductRepository, CategoryRepository) encapsulate EF Core operations and abstract database operations. The DbContext ties everything together for persistence.
• Utility functions (e.g., for sending emails or payment processing) are invoked by controllers or services within Web UI.
• The ASP.NET Core Identity system (located in Areas/Identity) is integrated within the BulkyWeb project; this component ensures authentication and authorization across the application.
Architectural Patterns and Design Principles
• MVC (Model-View-Controller): Clearly visible in the separation between BulkyWeb Controllers, Views (Razor pages), and the Domain Models.
• Repository and Unit of Work Patterns: Evident from the structure of Bulky.DataAccess in the subfolders for Repository, including interfaces and concrete classes. They abstract the database operations and enable cleaner unit testing.
• Code-First Migrations with EF Core: Shown by the Migrations folder and DbInitializer.
• Separation of Concerns by splitting the solution into multiple projects (DataAccess, Models, Utility, Web) for clarity and maintainability.
Detail Relevant Technologies
• ASP.NET Core MVC (.NET 8)
• Entity Framework Core (including code-first migrations)
• ASP.NET Core Identity for authentication/authorization
• Bootstrap v5 for UI design and responsiveness
• Stripe for payment processing
• Social login integrations (Google, Facebook)
• Deployment on Microsoft Azure