ASP.NET Core: The One Hour Makeover
summary
Starts a multi-project ASP.NET Core solution, adds global.json to lock SDK 2.1 and a shared Directory.Build.props for company/name/version, pushes to GitHub with an MIT license, then wires in analyzers, global tools like dotnet watch and dotnet-outdated, and MiniProfiler. Adds an xUnit functional-test project using Microsoft.AspNetCore.Mvc.Testing but must pin Microsoft.AspNetCore.App to 2.1 to load tests. Functional tests immediately catch a missing page (404). Adds a /health endpoint for runtime checks and uses LibMan to install Bootstrap 4 with CDN fallback.
AI-written summary · about
chapters (20)
- 0:00Start
- 4:42Core App Workshop
- 6:12Configure a Multi Project Solution
- 9:30Add in a Global Jason
- 11:22Adding Directory Build Props
- 22:46Dotnet Watch Workflow
- 23:51Dotnet Outdated
- 25:08Global Tools
- 26:04Configuring Functional Tests
- 27:26Functional Tests
- 40:19Health Checks
- 41:45Health Checks
- 42:03Microsoft Asp Net Core Diagnostics Health Checks
- 46:26Configure a Health Check
- 51:01Manage Client-Side Libraries
- 51:31Client-Side Library
- 53:25Updating an Existing Site
- 55:32Mini Profiler
- 56:42Web Optimizer
- 58:04Web Developer Checklist
related talks
38mStating the Obvious: Adding Non-functional Tests to CI
45mIt works on my machine! Logging and Metrics with .NET Core
01h 00mBuilding ASP.NET Core Kestrel
44mAzure Static Web Apps with Blazor and .NET
37mRock Your Code Code and App Performance for Microsoft .Net
50mI don't feel so well… Integrating health checks in your .NET Core solutions
08mBing runs on .NET Core 2.1
06mInterview