An Opinionated Approach to ASP.NET Core
summary
Opinionated guidance for ASP.NET Core projects: keep a repository top-level layout like src/tests/samples, check in development and deployment scripts, use Program.Main (between Build and Run) to run DB migrations and seeding, prefer feature folders or Razor Pages instead of huge controllers, use route attributes not conventional routes, favor tag helpers and view components, use webpack with npm or yarn and TypeScript, test end-to-end in memory with TestHost plus EF Core InMemory for smaller, higher-value test suites, and run Linux-based containers locally to catch platform issues.
AI-written summary · about
chapters (25)
- 0:00Start
- 1:14Solutions from Projects
- 3:51Adding a New Solution Folder
- 4:39Folder View
- 5:25Samples
- 6:44Unit Tests
- 7:54Ad Migration Script
- 8:20Deployment Scripts and Templates
- 8:40Azure Resource Manager
- 13:22Startup Code
- 21:29Project Structure
- 24:42Feature Folders
- 26:18Razor Pages
- 27:44Resetting Passwords
- 28:53Dependency Injection
- 35:47Security Policies
- 36:49Authorization Policy Builder
- 38:03View Components
- 39:18Webpack Configuration File
- 44:18Install a Typescript Compiler
- 44:39Typescript Config
- 46:02How Many Test Projects Should You Have
- 47:30How Do You Unit Test a Controller
- 50:09Asp Net Core Test Host
- 51:43Where Can You Mock Things Out
related talks
56mAn Opinionated Approach to ASP.NET Core
59mAn Opinionated Approach to ASP.NET Core
01h 01mAn Opinionated Approach to Using ASP.NET Core
56mAn Opinionated Approach to ASP.NET Core
59mClean Architecture With ASP.NET Core
57mClean architecture with ASP.NET Core
01h 02mPatterns for application development with ASP.NET Core
49mAn Opinionated, Maintainable REST API Architecture for ASP.NET Core