ASP.NET Core 2.0 MVC Razor Pages for Beginners How to Build a Website (Jonas Fagerberg)（Z-Library）

【One-Line Pitch】 A hands-on, no-fluff guide that teaches ASP.NET Core 2.0 by having you build three real web applications from scratch, culminating in a multi-project video-course site with a public MVC interface and a Razor Pages admin panel. Best for intermediate C# developers who know some HTML/CSS and want practical, job-relevant web-building skills fast. 【Book Arc】 - **Opening (~0%–10%)**: Sets expectations and prerequisites, then walks the project layout, file system, and `Startup.cs` — showing how to wire up configuration and register your first custom service. - **Early (~10%–30%)**: Builds the fundamentals of the request pipeline: middleware, exception handling, static files, MVC setup, controllers, routing (convention-based and attribute), actions, and an introduction to models and views. - **Early–Middle (~30%–40%)**: Introduces data persistence with Entity Framework Core 2.0 — the `DbContext`, migrations, database creation, and a SQL-backed data service — plus Razor views, layouts, tag helpers, partial views, and view components. - **Middle (~40%–55%)**: Moves into authentication and the second application: ASP.NET Identity configuration, registration, login/logout, and the start of the multi-project video-course solution with AutoMapper, DTOs, entities, and a mock repository. - **Late (~55%–75%)**: Builds the user-facing MVC application — membership controller, dashboard, course and video views, partials, and styling — connecting controllers to views through DTOs and view models. - **Ending (~75%–100%)**: Completes the solution with the Razor Pages administrator interface (index, create, edit, delete pages) for managing courses and users, tying the whole system together. 【Key Takeaways】 - **Services and dependency injection are the backbone of ASP.NET Core** (Opening): you register interfaces and implementations in `Startup.cs`, then consume them via constructor injection — the pattern repeats throughout the book. - **Middleware composes the request pipeline** (Early): understanding `IApplicationBuilder`, exception handling, and static-file serving is prerequisite to everything that follows. - **Routing and controllers define how URLs map to logic** (Early): both convention-based and attribute routing are covered, with `IActionResult` return types and model binding. - **Entity Framework Core handles persistence** (Early–Middle): the book walks through `DbContext`, migrations, and a data service abstraction rather than raw SQL. - **Razor views, layouts, tag helpers, partials, and view components** (Early–Middle) form the presentation toolkit for MVC, with `_Layout`, `_ViewStart`, and `_ViewImports` as the scaffolding files. - **Authentication via ASP.NET Identity** (Middle): registration, login/logout, and authorization attributes are implemented end-to-end. - **DTOs and view models decouple entities from the UI** (Middle): AutoMapper bridges them, keeping controllers and views clean. - **Razor Pages suit admin CRUD interfaces** (Ending): the administrator dashboard uses page-based index/create/edit/delete patterns, contrasting with MVC for the public site. 【Reading Tips】 - **Skim the table-of-contents-heavy opening** if you already know ASP.NET Core basics; the real value starts with middleware and services. - **Deep-read the Entity Framework and Identity chapters** — these are the hardest and most transferable parts; expect to re-read migration and configuration steps. - **Type the code, don't just read it**: the book is explicitly tactical, and the three-app progression only pays off if you build along. - **Use the first (empty-template) app to internalize DI and middleware** before the multi-project solution, where complexity jumps. - **Treat the Razor Pages admin section as a template** you can adapt to any CRUD back office. 【Coverage Limits】 This guide is based on stratified excerpts (front matter, table of contents, and chapter headings); specific code samples, exact API signatures, and detailed explanations within chapters are not fully represented. Percentages are approximate and derived from position markers.