~/talk

ASP.NET Core 1: What has changed for MVC and Web API developers?

Talkat NDC Oslo 2016 · 2016-06-08..06-10· [dotnet, web-platform]
slides:none on file

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

  1. 0:00Start
  2. 0:37Goal
  3. 0:58Contents
  4. 1:29NET Core
  5. 2:41Advantages
  6. 5:05Hosting
  7. 7:56Why a new ASP.NET?
  8. 8:52System.Web
  9. 10:48ASP.NET MVC Core 1
  10. 11:38Migration
  11. 12:55Middleware-Components
  12. 15:18Configuring the Pipeline
  13. 16:20Configuration considering the Environment
  14. 18:45Configuring Services
  15. 36:15HtmlHelpers in ASP.NET MVC 5
  16. 38:36Using TagHelpers
  17. 40:08Web APIs in MVC Core 1
  18. 43:30Web API with Attribute-based Routes
  19. 56:41Configuring MVC and Formatters
~/search
type to search 6,249 conferences, 138,987 speakers and 185,172 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.