How techoji/educationonline works
Project type and purpose
• This is a full-stack ASP.NET MVC web application (“Education Laboratory | Web site”) designed to support courses, labs, tests and administrative tasks for an online education platform.
• Key features include user authentication (ASP.NET Identity / OWIN), course and lab management, file uploads/downloads, Excel report generation (EPPlus) and data storage (Entity Framework + local SQL .mdf files).
File structure
• Top-level directories:
– App_Start: routing (RouteConfig), filters (FilterConfig), bundling (BundleConfig)
– Controllers: MVC controllers (AccountController, AdminController, LabController, PagesController)
– Models: business-domain models, EF contexts (ModelDB.edmx, shema.edmx), DbManager helper
– Views: Razor views (.cshtml) organized by area (Account, Admin, Lab, Pages, Shared)
– Content & Scripts: CSS/JavaScript (jQuery, custom modules, Modernizr)
– App_Data: local .mdf database files
– bin & packages: compiled assemblies and NuGet dependencies (EntityFramework, OWIN, EPPlus, etc.)
• Notice the classic layered MVC pattern and local database files under App_Data.
Main components and their interactions
a. Client Layer (Browser)
– HTML/CSS/JS served from the Views, Content, Scripts folders.
– Interacts with the server via HTTP (forms, AJAX calls, file uploads/downloads).
b. Web Server / Application Layer
– IIS / IIS Express hosting the ASP.NET MVC app.
– OWIN middleware pipeline handles authentication, static files, routing.
– Controllers implement endpoints and orchestrate UI and business logic.
c. Business Logic Layer
– Models and DbManager classes contain domain logic, file compression, lab pixel processing.
d. Data Access Layer
– Entity Framework 6 contexts (ModelDB, shema) map to SQL Server .mdf files in App_Data.
– Migrations and database scripts reside in the packages folder (EF tools).
e. External / Supporting Services
– Excel generation via EPPlus.
– Logging (antlR runtime), potential email/OAuth via OWIN security packages.
Architectural patterns & design principles
• MVC (Model-View-Controller) separation
• Layered architecture (Presentation → Business → Data)
• Dependency injection through OWIN startup (implicit via NuGet packages)
• Bundling & minification for static resources
• Code-first / Database-first approach via EDMX models