- We can place our code in individual source files in folder structures and wrap classes, interfaces, structs, and enums in namespaces that map to the folder structure.
- A class should have only one responsibility.
- You can comment in your code for document generators using XML comments placed directly above the public member to be documented.
- Cohesion is the logical grouping together of code that works on the same responsibility.
- Coupling refers to the dependencies between classes.
- Cohesion should be high.
- Coupling should be low.
- You can use DI and IoC to design for change.
- DI stands for Dependency Injection.
- IoC stands for Inversion of Control.
- Immutable objects are type-safe and so can be safely passed between threads.
- Objects should expose methods and properties and hide data.
- Data structures should expose data and have no methods. ...
Clean Code in C#
By :
Clean Code in C#
By:
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.
Related Content you might be interested in
Current Title:
Clean Code in C#
Table of Contents (17 chapters)
Preface
Coding Standards and Principles in C#
Free Chapter
Code Review – Process and Importance
Classes, Objects, and Data Structures
Writing Clean Functions
Exception Handling
Unit Testing
End-to-End System Testing
Threading and Concurrency
Designing and Developing APIs
Securing APIs with API Keys and Azure Key Vault
Addressing Cross-Cutting Concerns
Using Tools to Improve Code Quality
Refactoring C# Code – Identifying Code Smells
Refactoring C# Code – Implementing Design Patterns
Assessments
Other Books You May Enjoy
Customer Reviews