Book Image

Clean Code with C# - Second Edition

By : Jason Alls
4.5 (2)
Book Image

Clean Code with C# - Second Edition

4.5 (2)
By: Jason Alls

Overview of this book

Traditionally associated with Windows desktop applications and game development, C# has expanded into web, cloud, and mobile development. However, despite its extensive coding features, professionals often encounter issues with efficiency, scalability, and maintainability due to poor code. Clean Code in C# guides you in identifying and resolving these problems using coding best practices. This book starts by comparing good and bad code to emphasize the importance of coding standards, principles, and methodologies. It then covers code reviews, unit testing, and test-driven development, and addresses cross-cutting concerns. As you advance through the chapters, you’ll discover programming best practices for objects, data structures, exception handling, and other aspects of writing C# computer programs. You’ll also explore API design and code quality enhancement tools, while studying examples of poor coding practices to understand what to avoid. By the end of this clean code book, you’ll have the developed the skills needed to apply industry-approved coding practices to write clean, readable, extendable, and maintainable C# code.
Table of Contents (18 chapters)

AOP

AOP is a programming paradigm that aims to modularize and manage cross-cutting concerns in software systems. In traditional programming approaches, cross-cutting concerns, such as logging, security, transaction management, and error handling, tend to be scattered across different modules or components, leading to code duplication and tangled dependencies. AOP provides a way to encapsulate and centralize these concerns, making the code more modular, maintainable, and easier to understand.

At its core, AOP introduces a new construct called an “aspect.” An aspect represents a modular unit of cross-cutting functionality that can be applied to multiple parts of a system. It allows developers to separate concerns related to the core functionality of the system from cross-cutting concerns. This separation enhances code modularity and improves the system’s overall structure.

AOP achieves this separation by introducing the concept of “join points”...