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)

General recommendations

In this final section, we will look at some general recommendations from Microsoft for working on multi-threaded applications. They include the following:

  • Avoid using Thread.Abort to terminate other threads.
  • Use a mutex, ManualResetEvent, AutoResetEvent, and Monitor to synchronize activities between multiple threads.
  • Where possible, use a thread pool for your worker threads.
  • If you have any worker threads that gets blocked, then use Monitor.PulseAll to notify all the threads of a change in the worker thread's state.
  • Avoid using this, type instances, and string instances including string literals as lock objects. Avoid using types of the lock objects.
  • Instance locks can result in deadlocks, so exercise caution when using them.
  • Use the try/finally block with threads that enter a monitor so that in the finally block, you ensure that the thread leaves the monitor by calling...