Book Image

Clean Code in C#

By : Jason Alls
Book Image

Clean Code in C#

By: Jason Alls

Overview of this book

Traditionally associated with developing Windows desktop applications and games, C# is now used in a wide variety of domains, such as web and cloud apps, and has become increasingly popular for mobile development. Despite its extensive coding features, professionals experience problems related to efficiency, scalability, and maintainability because of bad code. Clean Code in C# will help you identify these problems and solve them using coding best practices. The book starts with a comparison of good and bad code, helping you understand the importance of coding standards, principles, and methodologies. You’ll then get to grips with code reviews and their role in improving your code while ensuring that you adhere to industry-recognized coding standards. This C# book covers unit testing, delves into test-driven development, and addresses cross-cutting concerns. You’ll explore good programming practices for objects, data structures, exception handling, and other aspects of writing C# computer programs. Once you’ve studied API design and discovered tools for improving code quality, you’ll look at examples of bad code and understand which coding practices you should avoid. By the end of this clean code book, you’ll have the developed skills you need in order to apply industry-approved coding practices to write clean, readable, extendable, and maintainable C# code.
Table of Contents (17 chapters)

Implementing structural design patterns

As programmers, we use structural patterns to improve the overall structure of our code. So, when code is encountered that lacks structure and is not at its cleanest, we can use the patterns mentioned in this section to restructure the code and make it clean. There are seven structural design patterns:

  • Adapter:Use this pattern to enable classes with incompatible interfaces to work cleanly together.
  • Bridge: Use this pattern to loosely couple code by decoupling an abstraction from its implementation.
  • Composite: Use this pattern to aggregate objects and provide a uniform way of working with individual and object compositions.
  • Decorator: Use this pattern to keep the interface the same while dynamically adding new functionality to the object.
  • Façade: Use this pattern to simplify larger and more complex interfaces.
  • Flyweight:Use this pattern to conserve memory and pass shared...