How zuyd-hogeschool/vlammend-varken-app works
Project Type and Purpose
• This is a full-stack ASP.NET Core solution for “Het Vlammend Varken,” a sustainable barbecue restaurant web app.
• It consists of:
• A Razor-Pages-based frontend (Vlammend_Varken project) for guest, waiter, and chef roles
• A C# Web API (Vlammend_Varken.API project) exposing REST endpoints
• A Core library (Vlammend_Varken.Core) containing domain models, EF Core DbContext, migrations, and business/data logic
• A MySQL database for persistent storage
File Structure Analysis
• Top-level solution (Vlammend_Varken.sln) references three projects:
• Vlammend_Varken (Razor Pages UI + Identity)
• Vlammend_Varken.API (Controllers for menu, orders, weather forecasts)
• Vlammend_Varken.Core (Models, Data/AppDbConnection, EF Core migrations)
• Config files (.json) handle environment settings, connection strings, Identity setup.
• wwwroot holds Bootstrap and jQuery for styling/validation.
README Insights
• Confirms roles (guest, ober, kok) and features: reservations, orders, payments, dynamic menus, stock overview.
• Tech stack: C#/.NET, MySQL, Razor UI, Bootstrap, jQuery, ASP.NET Identity.
Main Components & Interactions
a. Components:
1. Client Browser (Guest/Ober/Kok)
2. Razor Pages UI (Vlammend_Varken)
3. Web API (Vlammend_Varken.API)
4. Core Library (Vlammend_Varken.Core)
– AppDbConnection (EF Core DbContext)
– Domain Models & Migrations
5. MySQL Database
6. External Identity Service (ASP.NET Identity)
b. Relationships:
– Browser ↔ Razor UI via HTTPS
– Razor UI ↔ Web API (for AJAX or server-side calls to REST endpoints)
– Web API & Razor UI both reference Core library
– Core library → MySQL (via EF Core)
– Razor UI ↔ Identity (login/logout user management)
c. Architectural Patterns:
– Layered architecture: Presentation → API → Domain/Data → Database
– Separation of concerns: UI (Razor + Identity) vs. API vs. Business logic (Core)
– EF Core Code-First migrations for schema management
d. Key Technologies:
– ASP.NET Core Razor Pages
– ASP.NET Core Web API
– EF Core (AppDbConnection, migrations)
– MySQL
– ASP.NET Identity
– Bootstrap & jQuery
Detailing Essentials
• Flow for a typical use-case:
1. Guest logs in (Browser → Identity → Razor UI)
2. Browser requests menu (Razor UI → API → Core → DB → Core → API → Razor UI → Browser)
3. Guest places an order (Browser → Razor UI → API → Core → DB)
• Migration process (Core → Migrations → MySQL) to ensure DB schema versioning.