Skip to content

Web Fundamentals (for .NET Devs)

Cross-frontend fundamentals every senior .NET dev needs when collaborating across full-stack teams. Distinct from Frontend: Blazor, Frontend: React with .NET, and Frontend: MVC & Razor Pages, which are .NET-specific frontends and each lean on framework-shaped abstractions. This section is the substrate underneath all of them: the JavaScript runtime your Blazor JS interop calls into, the TypeScript types your React or Angular app is checked against, the CSS your MVC views or Razor components actually render, and the rendering models that make Blazor's render-mode taxonomy intelligible.

Treat this section as the "non-.NET fundamentals you can't avoid" — neither novice intro nor exhaustive frontend course. Senior-level depth, but tuned to a C#/.NET reader.

Topics (canonical order)

Why this order

Language layer first (JS, then TS), then presentation (CSS), then architecture (rendering models), then concrete framework integration (Angular). Each topic builds on the previous: TS makes no sense without JS; CSS layout patterns are referenced by the rendering-model trade-offs; rendering models frame how Angular fits next to a .NET API.

Cross-references

What this section is not

  • Not a tutorial. Skim if you already know JS/TS/CSS — use the gotchas + Q&A as a refresher.
  • Not framework-exhaustive. React lives in Frontend: React with .NET; Vue/Svelte/Solid are out of scope.
  • Not a build-tool deep dive. Webpack/Vite/esbuild internals are mentioned, not unpacked.