How martineza79/ecommercesite works
Project type and purpose
• This is a full-stack ASP.NET MVC 5 e-commerce demo application.
• It implements a layered architecture:
• WebUI layer (controllers/views/models)
• Domain layer (business interfaces and implementations)
• Persistence (Entity Framework + SQL Server)
• External services (SMTP/email)
File structure
• Top-level solution (ECommerceSite.sln) with two projects:
• ECommerceSite.Domain – contains Abstract (interfaces), Concrete (EF context, repos, order processing, auth), Entities, Migrations
• ECommerceSite.WebUI – ASP.NET MVC 5 application with App_Start (Ninject, routing), Controllers, Views, Models, Binders
• EF Migrations and App.config in Domain define DB schema and settings.
• Web.config, ApplicationInsights.config, Web.*.config in WebUI define environment settings.
README
• Confirms tech stack: C#, ASP.NET MVC 5, Razor, Bootstrap, EF (SQL Server), Ninject DI.
• Notes configurable EmailSettings for order notifications.
Main components
a. Client (Browser)
• UI rendered via Razor/Bootstrap
b. WebUI (ASP.NET MVC)
• Controllers (Account, Admin, Cart, Nav, Product)
• ViewModels/Models
• ModelBinders (CartModelBinder)
• DI Container (Ninject)
c. Domain Layer
• Interfaces: IProductRepository, IOrderProcess, IAuthentication
• Implementations: EFProductRepository (uses EFDbContext), EmailOrderProcess (uses EmailSettings), FormsAuthenticationProvider
d. Persistence
• EFDbContext → SQL Server database via ADO.NET
• Migrations for schema evolution
e. External/Infrastructure Services
• SMTP server for order emails
• (Optional) Application Insights telemetry
Relationships and data flows
1. Browser → HTTP → ASP.NET MVC middleware
2. MVC routing → Controller action
3. Controller calls injected Domain interface(s)
– IProductRepository → EFDbContext → SQL Server
– IOrderProcess → SMTP/email server
– IAuthentication → FormsAuth provider
4. Controller populates ViewModel → Razor View → HTML/CSS/JS → Browser
5. ModelBinders convert HTTP form data → strongly-typed Models (e.g., Cart)
Architectural patterns & design principles
• Layered architecture (UI → Domain → Data)
• MVC pattern in WebUI
• Repository pattern (IProductRepository + EF implementation)
• Dependency Injection/Inversion of Control (Ninject)
• Configuration-driven settings (EmailSettings, AppSettings, web.config transformations)
Detail
• EF Migrations as part of the build/deploy pipeline if relevant
• Call out configuration files that influence behavior (web.config, App.config, EmailSettings.cs)