dotnet-patterns

Topics in the source

• .NET Development Patterns
• When to Activate
• Core Principles
• 1. Prefer Immutability
• 2. Explicit Over Implicit
• 3. Depend on Abstractions
• Async/Await Patterns
• Proper Async Usage

Idiomatic C# and .NET patterns for building robust, performant, and maintainable applications. Writing new C# code Reviewing C# code Refactoring existing .NET applications Designing service architectures with ASP.NET Core Use records and init-only properties for data models. Mutability should be an explicit, justified choice. Be clear about nullability, access modifiers, and intent. Use interfaces for service boundaries. Register via DI container. Bind configuration sections to strongly-typed objects. Return explicit success/failure instead of throwing for expected failures. | Anti-Pattern | Fix | |---|---| | async void methods | Return Task (except event handlers) | | .Result or .Wait() | Use await | | catch (Exception) { } | Handle or rethrow with context | | new Service() in constructors | Use constructor injection | | public fields | Use properties with appropriate accessors | | dynamic in business logic | Use generics or explicit types | | Mutable static state | Use DI scoping or ConcurrentDictionary | | string.Format in loops | Use StringBuilder or interpolated string handlers |