Why should you care?

Pick the right tool: MVC for classic server-rendered sites with many controllers; Razor Pages for simpler page-based apps; Blazor for rich interactivity; Minimal APIs for microservices and SPAs.

See it live — copy this example

Create an MVC project (dotnet new mvc), add the code, and run dotnet run.

// MVC — ProductsController + Views/Products/Index.cshtml
// Razor Pages — Pages/Products/Index.cshtml with @page
// Minimal API — app.MapGet("/products", () => Results.Json(list));
// Blazor — Components/Counter.razor with @onclick

Run Example »

This lesson uses terminal or setup steps. Run commands on your computer — the live editor appears on coding lessons.

What happened?

• This course is MVC because it is the best map to most enterprise admin portals and teaches routing, filters, and Razor deeply.
• You can mix Minimal APIs in the same project later.

Try it yourself

1. Stay on MVC for ShopNest through lesson 50.
2. Skim Microsoft docs intro to Razor Pages — notice one file per page.
3. Note when your future app might add a Minimal API for mobile.
4. Change text or labels in the example and run again — watch the browser update.
5. Break the code on purpose (remove a semicolon), read the error message, then fix it.

Remember

MVC = controller + views — great for traditional sites. Razor Pages = simpler, page-centric. Blazor = SPA-style C#; Minimal APIs = lightweight HTTP.