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)

Chapter 9

  1. Application Programming Interface.
  2. Representational State Transfer.
  3. Uniform interface, client-server, stateless, cacheable, layered system, optional executable code.
  4. Hypermedia as the Engine of Application State (HATEOAS).
  5. RapidApi.com.
  6. Authorization and authentication.
  7. Claims are statements that an entity makes about itself. These claims are then validated against a data store. They are particularly useful in role-based security to check whether the entity making the claim is authorized in regard to that claim.
  8. Making API requests and examining their responses.
  9. Because you can change your data store in keeping with your requirements.