ASP.NET Core 1: What has changed for MVC and Web API developers?
summary
ASP.NET Core 1 unifies MVC and Web API into one framework, removes System.Web and changes low‑level APIs, and ships a middleware pipeline hosted by Kestrel (or WebListener/IIS as a reverse proxy) configured in Startup.Configure/ConfigureServices with built‑in DI. Project.json + JSON config and user secrets replace web.config. Routing drops Web API conventions—use attribute routes or the Web API compatibility shim for migration. Demo shows EF Core repository injection, JSON input/output, adding XML via NuGet, and returning 201 + Location via CreatedAtAction or custom IActionResult.
AI-written summary · about
chapters (19)
- 0:00Start
- 0:37Goal
- 0:58Contents
- 1:29NET Core
- 2:41Advantages
- 5:05Hosting
- 7:56Why a new ASP.NET?
- 8:52System.Web
- 10:48ASP.NET MVC Core 1
- 11:38Migration
- 12:55Middleware-Components
- 15:18Configuring the Pipeline
- 16:20Configuration considering the Environment
- 18:45Configuring Services
- 36:15HtmlHelpers in ASP.NET MVC 5
- 38:36Using TagHelpers
- 40:08Web APIs in MVC Core 1
- 43:30Web API with Attribute-based Routes
- 56:41Configuring MVC and Formatters
related talks
01h 01mASP.NET Core 3.0: State of the art
51mBuilding Web APIs with ASP.NET Core
01h 03mWhat you need to know about ASP.NET Core 2.2
16mASP.NET Core 2.2
48mWhat's new in ASP.NET Core 2.0?
01h 01mLessons learned building ASP.NET Core MVC
01h 01mWhat's New In ASP.NET Core
46mLet’s Get Minimal: .NET 6 New APIs in ASP.NET Core
