How santimacnet/fabrikamfiber-mvc works
Project type and purpose
• This is a full-stack ASP.NET MVC 5 web application (“FabrikamFiber.CallCenter”) designed for call-center training and demonstration.
• It consists of two main projects:
a. FabrikamFiber.DAL – a Data Access Layer implementing EF Code First repositories for Customers, Employees, Tickets, etc.
b. FabrikamFiber.Web – an MVC web front-end with controllers, views, client scripts (jQuery, Knockout, FullCalendar), CSS, and dependency injection via Ninject.
File structure
• Top-level solution (.sln) references two projects: DAL and Web.
• FabrikamFiber.DAL
• App.config – EF connection string to LocalDB
• Data folder – EF DbContext interface & implementation + individual repositories
• Models folder – POCO entity definitions (Customer, ServiceTicket, ScheduleItem, Alert, etc.)
• FabrikamFiber.Web
• App_Start/NinjectMVC3.cs – configures DI for controllers and repositories
• Controllers – MVC controllers for Customers, Employees, ServiceTickets, Reports, Home
• ViewModels – server-side models shaping data for views (DashboardViewModel, AssignViewModel, etc.)
• Views – Razor .cshtml templates organized by feature
• Scripts – jQuery, Knockout, FullCalendar, validation, unobtrusive AJAX
• Content – CSS, images, FullCalendar assets, fonts
• App_Data – LocalDB MDF/LDF files
• Deploy – simple batch script for deployment
• Web.config + transform files for debug/release
Main architectural components
• Web Browser (Client)
• UI layer built with Razor views, Knockout bindings, FullCalendar plugin, custom JS/CSS
• FabrikamFiber.Web (Web Application)
• MVC Controllers orchestrate user requests
• ViewModels adapt domain data for views
• Dependency Injection (Ninject) supplies IRepository<T> implementations
• FabrikamFiber.DAL (Data Access Layer)
• EF DbContext and Repositories encapsulate CRUD operations
• Domain Models represent database tables
• Database (SQL Server LocalDB)
• External Libraries/Frameworks
• ASP.NET MVC 5, Entity Framework 6, Ninject, jQuery, Knockout.js, FullCalendar
Relationships and data flow
• Client → HTTP Request → MVC Controller
• Controller → calls service/repository via injected IRepository
• Repository → EF DbContext → SQL Server LocalDB
• DbContext returns entities → Controller maps to ViewModel → Razor view renders HTML+JSON
• Client-side Knockout binds JSON data, FullCalendar displays schedules, AJAX calls Controllers for updates
Architectural patterns and design principles
• MVC (Model-View-Controller) separates concerns between UI, business logic, and data.
• Repository Pattern abstracts EF data access behind interfaces.
• Dependency Injection (Ninject) decouples controllers from concrete repositories.
• Code-First EF with configuration via App.config and database initializer.
• Client-side MVVM via Knockout.js for dynamic UI components.
Detail without over-fragmentation
• Logical component (Controllers, ViewModels, Repositories, DbContext).
• Critical dependencies (Controller → Repo → DbContext → Database).