ASP.NET Core for Angular, React, and Knockout developers
summary
Project templates ship with .NET Core 2.0 and wire up Webpack, HMR and testing so you get live TypeScript/LESS rebuilds and Hot Module Replacement for zero‑reload edits. Server execution of Angular/React components enables server-side prerendering that cuts perceived load from ~10s to ~2–3s on emulated 3G. A feature called HTTP priming avoids duplicate API calls by transferring server-fetched data into the client, and AOT publishing shrinks bundles (1.1MB → ~410KB) and halves startup CPU time. NodeServices runs NPM packages (SqueezeNet demo returns “beer glass” at ~92%).
AI-written summary · about
chapters (12)
- 0:00Introduction to SPAs
- 2:08ASP.NET Core templates
- 5:58Getting started with SPA
- 12:36Hot module replacement
- 15:43Server-side rendering
- 20:05HTTP priming for data
- 24:06Production publishing
- 31:21Debugging SPA applications
- 33:01Testing with Karma
- 38:56Webpack configuration
- 50:00Node services and AI
- 1:01:32Conclusion and resources
related talks
59mASP.NET Core for Angular, React, and Knockout developers
54mBuilding applications with Angular and ASP.NET Core
25mKeynote
27mAngular Renaissance
47mAn in-flight port from Angular to React, a tale of performance and happiness
20mAngular Renaissance
20mTools for Fast Angular Applications
21mWhere & How You Write Your Code