Anonymized case study. Client name and identifying metrics are withheld. Patterns reflect representative senior .NET programs.
Executive summary
A logistics enterprise operated a WebForms intranet with duplicated CSS and inconsistent auth claims. Product wanted faster feature delivery without rewriting every screen at once.
The challenge
Hundreds of WebForms pages with view-state heavy postbacks. Designers lacked a shared component vocabulary. Security required fine-grained policies per business unit.
Technical approach
Blazor shell with OIDC and policy-based authorization, shared RCL design system, WASM islands for interactive grids, strangler routing for unmigrated pages, and bUnit smoke tests on critical components.
Outcomes
Priority workflows moved to Blazor within two release trains. Support tickets for auth loops dropped after claims mapping was centralized. Teams shipped UI features without CSS archaeology.
Discuss a program like this
Share your constraints and stack—we will outline fit and what proof we can share on a discovery call.