To get the most out of this book

The majority of the chapters can be read independently of each other and in any order. But to get the most out of this book, I recommend that you read the chapters in the order presented. As you work through the chapters, follow the instructions, and carry out the tasks presented. Then, when you reach the end of a chapter, answer the questions and carry out the recommended further reading to reinforce what you have learned. For maximum benefit when working through the contents of this book, it is recommended that you meet the following requirements:

It will be useful if you have these in place before you start reading and working your way through the chapters.

If you are using the digital version of this book, we advise you to type the code yourself or access the code via the GitHub repository (link available in the next section). Doing so will help you avoid any potential errors related tothe copying and pasting of code.

You should have basic experience of using Visual Studio 2019 Community Edition or higher, and basic C# programming skills, including writing console applications. Many examples will be in the form of C# console applications. The main project will be using ASP.NET. It will help if you are capable of writing ASP.NET websites using the framework and core. But don't worry – you will be guided through the steps that you need to go through.

Download the example code files

You can download the example code files for this book from your account atwww.packt.com. If you purchased this book elsewhere, you can visitwww.packtpub.com/supportand register to have the files emailed directly to you.

You can download the code files by following these steps:

1. Log in or register atwww.packt.com.
2. Select theSupporttab.
3. Click onCode Downloads.
4. Enter the name of the book in theSearchbox and follow the onscreen instructions.

Once the file is downloaded, please make sure that you unzip or extract the folder using the latest version of:

• WinRAR/7-Zip for Windows
• Zipeg/iZip/UnRarX for Mac
• 7-Zip/PeaZip for Linux

The code bundle for the book is also hosted on GitHub athttps://github.com/PacktPublishing/Clean-Code-in-C-. In case there's an update to the code, it will be updated on the existing GitHub repository.

We also have other code bundles from our rich catalog of books and videos available athttps://github.com/PacktPublishing/. Check them out!

Download the color images

We also provide a PDF file that has color images of the screenshots/diagrams used in this book. You can download it here:https://static.packt-cdn.com/downloads/9781838982973_ColorImages.pdf.

Conventions used

There are a number of text conventions used throughout this book.

CodeInText:Indicates code words in text, database table names, folder names, filenames, file extensions, pathnames, dummy URLs, user input, and Twitter handles.Here is an example:"The InMemoryRepository class implements theGetApiKey()method ofIRepository. This returns a dictionary of API keys. These keys will be stored in our_apiKeysdictionary member variable."

A block of code is set as follows:

using CH10_DividendCalendar.Security.Authentication;
using System.Threading.Tasks;

namespace CH10_DividendCalendar.Repository
{
    public interface IRepository
    {
        Task<ApiKey> GetApiKey(string providedApiKey);
    }
}

Any command-line input or output is written as follows:

          az group create --name "<YourResourceGroupName>" --location "East US"
        

Bold: Indicates a new term, an important word, or words that you see onscreen. For example, words in menus or dialog boxes appear in the text like this. Here is an example: "To create the app service, right-click the project you created and select Publish from the menu."