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)

Overview of behavioral design patterns

As a programmer, your behavior on the team is governed by your methods of communication and interaction with other team members. The objects we program are no different. As programmers, we determine how objects will behave and communicate with other objects through the use of behavioral patterns. These behavioral patterns are as follows:

  • Chain of responsibility: A sequential pipeline of objects that process an incoming request.
  • Command: Encapsulates all the information that will be used to call a method at some point in time within an object.
  • Interpreter: Provides interpretation of a given grammar.
  • Iterator: Use this pattern to access an aggregate object's elements sequentially without exposing its underlying representation.
  • Mediator: Use this pattern to have objects communicate with each other via an intermediary.
  • Memento: Use this pattern to capture and save the object...