.NET overview: reading path
The .NET section explains the platform underneath C#: what the runtime and SDK do, the building blocks every service uses, and how the releases fit together. It is deliberately short: four pages, read in order.
Reading path
Section titled βReading pathβ| Step | Page | What you get from it |
|---|---|---|
| 1 | What is .NET? | Runtime, base class library and SDK; modern .NET versus .NET Framework; which application framework fits which app; your first program. |
| 2 | .NET core features | Dependency injection lifetimes, the middleware pipeline, Minimal APIs with .NET 10 validation, and Native AOT, each with a runnable sample. |
| 3 | .NET versions | Every release on one table with support status (.NET 10 LTS and .NET 11 STS are supported in November 2026). |
| 4 | .NET evolution | The history from .NET Framework 1.0 to .NET 11, release by release. |
Browse by question
Section titled βBrowse by questionβ| If your question isβ¦ | Read |
|---|---|
| βShould this new app use .NET Framework or .NET?β | NET and NET Framework |
| βWhich framework do I use for a desktop, mobile or web app?β | Application frameworks |
| βWhy is my scoped service behaving like a singleton?β | Dependency injection |
| βWhy does authorization run before the user is known?β | Middleware |
| βHow do I validate a request body in a Minimal API?β | Minimal APIs |
| βWill Native AOT make my container start faster?β | Native AOT |
| βWhich versions are still supported?β | .NET versions |
Where to go next
Section titled βWhere to go nextβ- C#: the language, from basics to C# 15.
- ASP.NET Core Web API: controllers, routing, the request pipeline and DTO design.
- Software architecture and design patterns: structuring larger .NET applications.
- Testing: unit, integration and end-to-end tests for .NET and other stacks.