Coding Standards

C# coding standards mandate enabling nullable reference types and following strict async/await patterns to prevent deadlocks. These practices ensure robust error handling and maintain consistent code quality across services.

Organizing C# services, models, and ViewModels requires adhering to defined class patterns and file size limits. This structure separates business logic from data representation to improve project maintainability.

Setting up dependency injection and configuration involves registering services in the DI container and binding settings from configuration files. This approach enforces loose coupling and centralizes management of application parameters.

Standard error handling in C# .NET applications requires implementing descriptive error messages and proper exception catching. This ensures failures are traceable and prevents unhandled crashes during async operations.

Yes, refactoring C# code requires following established naming conventions and type annotations to maintain consistency. Adhering to these standards reduces bugs and ensures the codebase remains easily understandable.

These C# coding standards are designed for the Nexus Agent project but provide a strong baseline for any .NET application. The patterns for dependency injection, file organization, and error handling are universally applicable.