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)

Chapter 5

  1. A checked exception is an exception that is checked at compile time.
  2. An unchecked exception is an exception that is not checked or simply ignored at compile time.
  3. An overflow exception is raised when high-order bits cannot be assigned to the destination type. In checked mode, OverflowException is raised. In unchecked mode, high-order bits that cannot be assigned are simply ignored.
  4. An attempt made to access a property or a method on a null object.
  1. Implement a Validator class and an Attribute class that checks the parameter for null, and that throws ArgumentNullException. You would use the Validator class at the top of your methods so that you don't get halfway through the method before the exception is raised.
  2. Business Rule Exception (BRE).
  3. BREs are bad practice because they expect exceptions to be raised in order to control program flow.
  4. Correct programming should...