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)

Understanding the testing tools

The testing tools we'll be looking at within Visual Studio are MSTest, NUnit, Moq, and SpecFlow. Each testing tool creates a console application and the relevant test project. NUnit and MSTest are unit testing frameworks. NUnit is much older than MSTest, and so has a more mature and full-featured API compared to MSTest. I personally prefer NUnit over MSTest.

Moq is different from MSTest and NUnit as it is not a testing framework but a mocking framework. A mocking framework replaces the real classes in your project with mock (fake) implementations that are used for testing purposes. You can use Moq together with MSTest or NUnit. And finally, SpecFlow is a BDD framework. You start by writing a feature in a feature file using business language that the user and the techy alike will understand. Then a step file is generated for that feature. The step file contains the methods as steps necessary to implement that feature.

By the...