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)

Integrating tests into the continuous integration and deployment (CI/CD) pipeline

Integrating unit tests into your CI/CD pipeline can help ensure that your code is always tested and that any changes made to the code base do not introduce new bugs. Here are some steps you can take to integrate unit tests into your CI/CD pipeline:

  1. Write your unit tests using a testing framework that can be automated, such as NUnit, MSTest, or xUnit.
  2. Set up a build server that can automatically run your unit tests whenever code changes are made to your repository. Most build servers, such as Jenkins, Travis CI, GitHub Actions, and Azure DevOps, support running unit tests as part of the build process.
  3. Configure your build server to automatically build and test your code whenever new commits are pushed to your repository. This will ensure that your unit tests are always up to date and that your code is tested as soon as changes are made.
  4. Set up a code coverage analysis tool to measure...