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 static constructors and methods

If multiple classes require access to a property instance simultaneously, then one of the threads will be requested to run the static constructor (also known as the type initializer). While waiting for the type initializer to run, all the other threads will be locked. Once the type initializer has run, the locked threads are unlocked and are able to access the Instance property.

Static constructors are thread-safe as they are guaranteed to run only once per application domain. They are executed before accessing any static members and before any class instantiation is performed.

Should an exception be raised in and escape from a static constructor, then TypeInitializationException is generated, which causes the CLR to exit your program.

Before any threads can access a class, static initializers and static constructors must finish executing.

Static methods only keep a single copy of the method and its...