api-conventions

ASP.NET Core API conventions standardize controller structure by enforcing specific route naming, authentication patterns, and endpoint templates. This ensures architectural consistency when adding new controllers or modifying existing endpoints in your Api/ project.

Validation in ASP.NET Core APIs is handled by integrating FluentValidation to validate DTOs. This approach enforces consistent error-handling patterns and ensures data integrity before processing requests within your controller endpoints.

DTO mapping in an ASP.NET Core API project uses static mappers to transform data transfer objects into domain models. This standardizes mapping patterns and maintains separation between API layers and internal business logic.

Yes, these API conventions are specifically designed for ASP.NET Core .NET 10 projects. They provide the necessary guidelines for routing, authentication, and error-handling to maintain maintainable architecture in modern .NET environments.

You need to apply API conventions whenever modifying authentication or error-handling logic within the Api/ project. This ensures that any updates to security patterns or error responses remain consistent with the established controller structure.