Book Image

Clean Code with C# - Second Edition

By : Jason Alls
4.5 (2)
Book Image

Clean Code with C# - Second Edition

4.5 (2)
By: Jason Alls

Overview of this book

Traditionally associated with Windows desktop applications and game development, C# has expanded into web, cloud, and mobile development. However, despite its extensive coding features, professionals often encounter issues with efficiency, scalability, and maintainability due to poor code. Clean Code in C# guides you in identifying and resolving these problems using coding best practices. This book starts by comparing good and bad code to emphasize the importance of coding standards, principles, and methodologies. It then covers code reviews, unit testing, and test-driven development, and addresses cross-cutting concerns. As you advance through the chapters, you’ll discover programming best practices for objects, data structures, exception handling, and other aspects of writing C# computer programs. You’ll also explore API design and code quality enhancement tools, while studying examples of poor coding practices to understand what to avoid. By the end of this clean code book, you’ll have the developed the skills needed to apply industry-approved coding practices to write clean, readable, extendable, and maintainable C# code.
Table of Contents (18 chapters)

Summary

We started with an overview of exception handling in C#. We saw there are two types of exceptions: System.Exception and System.ApplicationException. System.Exception is the base class for all exceptions in the .NET Framework, while System.ApplicationException is the base class for all application-specific exceptions.

Then, we moved on to review clean code exception handling using the SRP, OCP, and DIP. We saw how these principles help to keep our code clean, readable, extendable, and maintainable.

Next, we looked at best practices for exception handling. By following these best practices, we saw how we can write more robust and reliable code that handles exceptions effectively and helps us to diagnose and fix issues more quickly.

We then moved on to look at some common exception-handling mistakes and how we can avoid them. By avoiding these common mistakes, we can write cleaner, more reliable code that is easier to maintain and debug.

Next, we looked at various...