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)

Avoiding NullPointerExceptions

NullReferenceException is a common exception that has been experienced by most programmers. It is thrown when an attempt is made to access a property or method on a null object.

To defend against computer program crashes, the common course of action among fellow programmers is to use try{...}catch (NullReferenceExceptionre){...} blocks. This is a part of defensive programming. But the problem is that, a lot of the time, the error is simply logged and rethrown. Besides this, a lot of wasted computations are performed that could have been avoided.

A much better way of handling ArgumentNullExceptions is to implement ArgumentNullValidator. The parameters of a method are usually the source of a null object. It makes sense to test the parameters of a method before they are used and, if they are found to be invalid for any reason, to throw an appropriate Exception. In the case of ArgumentNullValidator, you would place this validator at the...