aspnet-core

To build an ASP.NET Core web app, follow guided workflows that map development tasks to official Microsoft Learn guidance, ensuring up-to-date documented patterns for program structure, security, data access, testing, and deployment.

Choosing between Blazor, Razor Pages, MVC, and Minimal APIs starts with a stack selection workflow that aligns your app requirements with documented ASP.NET Core models, providing primary app-model references and cross-cutting guidelines for each option.

Yes, this guidance covers upgrading and refactoring existing ASP.NET Core applications by centralizing versioning and upgrade considerations, enforcing current documented patterns to minimize breaking changes and reduce operational risk during the process.

Configure security and deployment for ASP.NET Core APIs, SignalR, and gRPC by applying cross-cutting guidelines from official Microsoft Learn references, enforcing documented patterns for authentication, authorization, and pipeline configuration across all app models.

The limitation of relying on official Microsoft Learn guidance for ASP.NET Core is that it strictly enforces documented patterns, which may not cover highly custom or undocumented edge cases outside the standard Blazor, MVC, or Minimal API workflows.

You need official guidance for ASP.NET Core Minimal APIs and gRPC development when building, reviewing, or upgrading services, ensuring your program structure, routing, and data access patterns align with current documented best practices.