dotnet-aspnet-core

ASP.NET Core middleware follows a canonical order: exception handling, HSTS, HTTPS redirection, static files, routing, CORS, authentication, authorization, and endpoints. Ordering middleware correctly prevents security bypasses and ensures reliable request processing.

ASP.NET Core dependency injection uses the options pattern to bind strongly typed configuration classes. Register services with appropriate lifetimes and validate environment-specific settings during startup to enforce consistent configuration management across web apps.

ASP.NET Core security anti-patterns include insecure default configurations, misordered authentication middleware, unrestricted CORS policies, and missing rate-limiting. Apply security hardening guidance for headers, authentication, and authorization to avoid these vulnerabilities.

ASP.NET Core auditing applies these patterns to existing projects by reviewing hosting, middleware, security, and configuration. It specifies concrete templates and anti-patterns to identify architecture issues and implement recommended improvements during code review.

ASP.NET Core hosting ambiguity and configuration issues arise from inconsistent environment-specific settings and misapplied dependency injection. Resolving these requires applying standardized options patterns, canonical hosting setups, and proper DI registration practices.