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)

Working with parallel threads using semaphores

In multi-threaded applications, a non-negative number, known as a semaphore, is shared between threads that have a number of 1 or 2. In terms of synchronization, 1 specifies wait and 2 specifies signal.We can associate a semaphore with a number of buffers, which can each be worked on simultaneously by different processes.

So, essentially, semaphores are signaling mechanisms of the integer and binary primitive types that can be modified by wait and signal operations. If there are no free resources, then processes that require a resource should execute the wait operation until the semaphore value is greater than 0. Semaphores can have multiple program threads and they can be changed by any object, obtaining a resource or releasing it.

The advantages of using semaphores are down to the fact that more than one thread can access the critical piece of code. A semaphore is executed in the kernel and is machine-independent...