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)

The proxy pattern

The proxy pattern is a structural design pattern providing objects that act as substitutes for real service objects used by clients. Proxies receive client requests, perform the required work, and then pass the request to service objects. Proxy objects are interchangeable with services as they share the same interfaces:

An example of when you would want to use the proxy pattern is when you have a class that you do not want to change, but where you do need additional behaviors to be added. Proxies delegate work to other objects. Unless a proxy is a derivative of a service, proxy methods should finally refer to a Service object.

We will look at a very simple implementation of the proxy pattern. Add a folder to the root of your Chapter 11 project called ProxyPattern. Add an interface called IService with a single method to handle a request:

public interface IService {
void Request();
}

TheRequest()method...