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)

Factories

Factories are implemented using the factory method pattern. The intent of this pattern is to allow the creation of objects without specifying their classes. This is accomplished by invoking a factory method. The main goal of a factory method is to create an instance of a class.

You use the factory method pattern for the following scenarios:

  • When the class is unable to anticipate the type of object that must be instantiated
  • When the subclass must specify the type of object to instantiate
  • When the class controls the instantiation of its objects

Consider the following diagram:

As you can see from the preceding diagram, you have the following items:

  • Factory, which provides the interface for the FactoryMethod() that returns a type
  • ConcreteFactory, which overrides or implements the FactoryMethod() to return a concrete type
  • ConcreteObject...