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

In this chapter, you saw how code metrics provide several measurements of code quality, and how easy it is to generate them. Code metrics include the number of lines – including blank lines – versus the number of executable lines of code, the cyclomatic complexity, the level of cohesion and coupling, and how maintainable your code is. The refactoring color codes are green for “good”, yellow for “ideally needs refactoring”, and red for “definitely needs refactoring”.

You then saw how easy it is to provide a static code analysis of projects and view the results. Viewing and modifying rulesets that govern what gets analyzed and what doesn’t get analyzed was also covered. Then, you experienced quick actions and learned how to perform bug fixes, add using statements, and refactor code with a single command.

Then, we used the JetBrains dotTrace profiler to measure our application’s performance, track down...