Blazor - SPA from ASP.NET Family
Author - Abdul Rahman (Bhai)
Talk
1 Articles
Table of Contents
What we gonna do?
With modern web apps, building a rich UI is hard. We normally use javascript to build a rich UI with the limitation of not being able to reuse server side code. In today's session let's learn what Blazor is and how it differs from Javascript SPA like angular, react or vue.
Why we gonna do?
As a .NET developer, switching context between C# on the server and JavaScript on the client adds friction and slows down development. Blazor bridges this gap by letting you write rich, interactive UI entirely in C# — sharing models, validation logic, and business rules across both client and server without duplicating code.
Unlike JavaScript SPAs, Blazor gives you the full power of the .NET ecosystem — type safety, tooling, and familiar patterns — while still delivering a modern single-page application experience.
How we gonna do?
Watch the talk to explore how Blazor fits into the ASP.NET family, how it compares to JavaScript frameworks like Angular, React, and Vue, and how you can start building SPAs using only C# and .NET.
Summary
In this talk, we explored what Blazor is and how it positions itself as a first-class SPA framework within the ASP.NET family. We compared it to popular JavaScript frameworks and highlighted how .NET developers can leverage their existing skills to build modern web UIs without leaving the .NET ecosystem.