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)

Modularization

A system consists of one or more modules. When a system con two or more modules, you need to test the interaction between them to make sure they work together as expected. Let's consider the system for an API shown in the following diagram:

As you can see from the previous diagram, we have a client that accesses a data store in the cloud via an API. The client sends a request to the HTTP server. The request is authenticated. Once it has been authenticated, the request is then authorized to access the API. The data sent by the client is deserialized and then passed on to the business layer. The business layer then performs either a read, insert, update, or delete operation on the data store. The data is then passed back to the client from the database via the business layer, followed by the serialization layer, and then back to the client.

As you can see, we have a number of modules that interact with each other....