Learning path

This tutorial follows one main sequence; it is not a reference manual to browse at random. Each chapter builds on the chapters before it:

• Parameter binding from Requests and responses is the foundation for every endpoint that follows.
• Data access uses dependency injection and configuration from Application structure.
• Authentication and authorization in Security are inserted into the middleware pipeline.

So please read the chapters in order. Each chapter corresponds to a separate, complete, runnable project in the repository's samples/ directory. You can open the matching example at any time and compare it with your own code.

About the samples

Both editions use the same runnable projects. Code comments, sample data, and application messages are in English, so commands and responses match in either edition.

6 stages, 24 chapters · 24 available.

1. 01

   Getting started

   Set up your tools, meet C#, and run your first endpoint

   • 00Environment setup
   • 01A quick tour of C#
   • 02First steps
2. 02

   Requests and responses

   Read request data and return useful responses

   • 03Path parameters
   • 04Query parameters
   • 05Request bodies
   • 06Validation
   • 07Headers and cookies
   • 08Response types
   • 09Status codes and errors
   • 10Route groups
3. 03

   Application foundations

   Connect services, manage configuration, and understand the pipeline

   • 11Dependency injection
   • 12Configuration and options
   • 13Middleware
   • 14Logging
4. 04

   Data access

   Store data in SQLite with EF Core and build a complete API

   • 15EF Core basics
   • 16Relationships and queries
   • 17A complete CRUD API
5. 05

   Security

   Identify callers and decide what they can do

   • 18Authentication (JWT)
   • 19Authorization
   • 20CORS
6. 06

   Going live

   Test your API, organize its code, and deploy it

   • 21Testing
   • 22Organizing by feature
   • 23Publishing and deployment

How to read each page

Every page follows the same structure. Once you are familiar with it, you will be able to move through the material quickly:

1. Complete code: The page starts with the finished program for the chapter. You can copy and run it first to see what it does.
2. Run and verify: Commands and expected output help confirm that your environment and results are correct.
3. Walkthrough: Highlighted lines show what was added or changed, with an explanation of what each part does and why it is designed that way.
4. Summary: A few key points recap the chapter and link to the next page.

The pages use four callout types with consistent meanings:

Tip

Practical advice to help you avoid common detours.

Technical detail

Background on how things work. You can skip it on your first read without affecting the rest of the material.

Note

A common pitfall that is worth reading carefully.

FastAPI comparison

If you have used FastAPI, this callout briefly explains the corresponding concept. If you have not, feel free to skip it.