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)

Using quick actions

Another handy tool that I like to use is the Quick Action tool. Appearing as a screwdriver , a lightbulb , or an error light bulb on a line of code, quick actions enable you to use a single command that will generate code, refactor code, suppress warnings, perform code fixes, and add using statements.

Since the CH10_AddressingCrossCuttingConcerns project had 32 warnings and 13 messages, we can use this project to see the quick actions in action. Have a look at the following screenshot:

Looking at the preceding screenshot, we see the lightbulb on line 10. If we click on the lightbulb, the following menu pops up:

If we click on Add readonly modifier, the readonly access modifier is placed after the private access modifier. Have a go yourself at using quick actions to modify the code. It is fairly straightforward once you get the hang of it. Once you have had a play around with...