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)

Using a mutex with synchronous threads

In C#, a mutex is a thread-locking object that works across multiple processes. Only a process that can request or release a resource can modify the mutex. When a mutex is locked, the process will have to wait in a queue. When the mutex is unlocked, then it can be accessed. Multiple threads can use the same mutex, but only in a synchronous manner.

The benefits of using a mutex are that a mutex is a simple lock obtained before entering a critical piece of code. That lock is released when the critical piece of code is exited. Because only a single thread is in the critical piece of code at any one time, the data will remain in a consistent state as there will be no race conditions.

There are several disadvantages to using a mutex:

  • Thread starvation occurs when a thread is unable to move forward as an existing thread has obtained a lock and has either gone to sleep or is pre-empted (prevented from completing...