Enterprise Angular guides for .NET developers — Signals, NgRx, SSR, Reactive Forms validation with ProblemDetails, OnPush change detection, and RxJS.
Practical Angular guides built for enterprise SPAs backed by ASP.NET Core APIs. Start with Angular and .NET integration or dive into state, SSR, and reactive forms below.
Introduction
This page is the article map for building enterprise Angular SPAs backed by ASP.NET Core APIs.
Angular and ASP.NET Core integration habits — DTO contracts, error envelopes, pagination metadata, datetime policy, and CORS decisions that stop frontend-backend rework.
Map ASP.NET Core ProblemDetails and FluentValidation field errors onto Angular Reactive Forms — FormGroup patterns, setErrors, submit UX, interceptors, and tests. Not a FluentValidation server tutorial.
Angular Signals for API-driven apps — load state from ASP.NET Core, computed UI flags, RxJS interop, and when Signals beat BehaviorSubject for SPA state.
OnPush rerenders a component when an input identity changes, an event fires, or a signal updates. Mutating an object in place does not. This is the change-detection page, not the signals guide and not the interview list.
Host Angular SSR or prerender with an ASP.NET Core API — process layout, cookies and TransferState, MapFallbackToFile vs API routes, App Service/container deploy sketch, and when SSR is not worth it for SaaS shells.
Angular state management decision for ASP.NET Core backends — local Signals, SignalStore for entity CRUD, and when classic NgRx Effects still win. Complements the Signals how-to; does not rewrite it.
Which RxJS map to use when Angular calls an ASP.NET Core API: switchMap for search, exhaustMap for submit, concatMap when order matters. The wrong one drops or doubles the request.
When an Angular app should bootstrap with standalone components instead of NgModules, and how provideHttpClient and provideRouter replace the old imports.