.NET Best Practices and Design Patterns

Implementing business logic maintaining a Separation of Concerns

• Programming to the most modern versions of industry recognized design patterns
• Organizing and isolating application layers with key strategic architectural patterns
• Following Agile quality principles through automated unit tests and Test-Driven development

Applying S.O.L.I.D. principles of class design

• Single Responsibility
• Open-Closed
• Liskov Substitution
• Interface Segregation
• Dependency Inversion

Enhancing code quality and maintainability

• Automating design reviews with Code analysis
• Obtaining code metrics to ensure maintainability

Applying simple interfaces to intricate algorithms

• Unifying interfaces from subsystems for ease of use and reusability
• Implementing the Façade and Lazy Singleton patterns

Provide support for multiple concurrent views with dynamic notification

• Avoid timed polling and update the user interface or other clients only when data changes
• Deploying the modern Strategy pattern using delegates and state change invocation

Apply modern tactical design patterns to insure SOLID application design

• Varying application logic dynamically with the Strategy pattern to enhance reuse and flexibility
• Achieving loose coupling using the Abstract Factory pattern for dependency injections
• Eliminating code duplication by employing the Template Method pattern
• Reducing logic complexity with polymorphism and the State pattern

Reducing application stalls and delays for better performance and improved user experience

• Leveraging C# async and await keywords to easily implement asynchronous threads
• Harnessing the Adapter pattern for mismatched interfaces and behavior
• Managing data concurrency collisions with "everyone wins" scenarios
• Maximizing performance by implementing the Dispose patter

Automating unit testing

• Shortening development cycles with automated tests
• Eliminating regression errors with reusable tests

Integrating testing and coding

• Applying the test–first programming practice
• Generating immediate red–green feedback for increased code quality and shortened feature development cycles
• Organizing, coordinating and running test cases
• Isolating a class test environment with the Mock–Object pattern for reliable and repeatable testing
• Tracking the Red–Green–Refactor rhythm for feedback

Refactoring code to improve design

• Improving design with by refactoring
• Eliminating code duplication by refactoring to patterns

Designing the application architecture

• Layering architectures for reusability, durability and scalability
• Decoupling object creation with the Factory pattern
• Preserving object identity with the Identity Map pattern

Maintaining Separation of Concerns for each application layer

• Isolating the data tier with the Entity Framework and the Lazy Repository pattern
• Supporting independent view layers with the MVC architecture and State pattern
• Comparing alternative strategic patterns including MVP and MVVM