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)

Best practices for handling exceptions

Here are some best practices for handling exceptions in C#:

  • Only catch exceptions that you can handle: Catching exceptions that you cannot handle can result in hiding the root cause of the exception and can lead to difficult-to-debug issues. Only catch exceptions that you can handle, and let the ones that you cannot handle propagate up the call stack.
  • Use try-catch blocks sparingly: While try-catch blocks can be useful for handling exceptions, they can also negatively impact the performance of your application. Use them sparingly and only when necessary.
  • Use specific exception types: Catching general exceptions such as System.Exception can make it difficult to determine the root cause of the exception. Instead, catch specific exception types that are relevant to your application.
  • Log exceptions: Logging exceptions can help you diagnose issues and fix bugs in your application. Use a logging framework such as log4net or Serilog...