Blazor

E182231

.NET web framework single-page application framework web framework

Blazor is a Microsoft web framework that enables developers to build interactive client-side web UIs using C# and .NET instead of JavaScript.

Try in SPARQL Jump to: Surface forms Disambiguation Statements Elicitation Referenced by

All labels observed (6)

Label	Occurrences
Blazor canonical	5
ASP.NET Core Blazor	1
Blazor Hybrid	1
Blazor Server	1
Blazor United (ASP.NET Core full-stack UI)	1
Blazor WebAssembly	1

How this entity was disambiguated

This entity first appeared as the object of triple T1610532 — resolving that mention is where its identity was fixed. The disambiguator weighed these candidate entities and picked the highlighted one (or “None”, minting a new entity). This is how homonymy is resolved: the same surface form can point to different entities.

NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07

Target entity: Blazor
Context triple: [ASP.NET, includesComponent, Blazor]

A. Svelte
Svelte is a modern JavaScript framework and compiler for building user interfaces that shifts much of the work to a build step, producing highly efficient, minimal runtime code.
B. .NET Core
.NET Core is a cross-platform, open-source, modular implementation of the .NET platform designed for building modern, cloud-based, and high-performance applications.
C. Xamarin
Xamarin is a cross-platform mobile app development framework that allows developers to build native iOS, Android, and Windows applications using C# and .NET.
D. SvelteKit
SvelteKit is a full-stack application framework for building fast, modern web apps with the Svelte UI library, offering routing, server-side rendering, and deployment tooling.
E. Next.js
Next.js is a popular React-based framework for building server-rendered and statically generated web applications with features like routing, API routes, and performance optimizations built in.
F. None of above. chosen
G. Unsure - the case is ambiguous/there is not enough information to decide.

NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07

Target entity: Blazor
Target entity description: Blazor is a Microsoft web framework that enables developers to build interactive client-side web UIs using C# and .NET instead of JavaScript.

A. Svelte
Svelte is a modern JavaScript framework and compiler for building user interfaces that shifts much of the work to a build step, producing highly efficient, minimal runtime code.
B. .NET Core
.NET Core is a cross-platform, open-source, modular implementation of the .NET platform designed for building modern, cloud-based, and high-performance applications.
C. Xamarin
Xamarin is a cross-platform mobile app development framework that allows developers to build native iOS, Android, and Windows applications using C# and .NET.
D. SvelteKit
SvelteKit is a full-stack application framework for building fast, modern web apps with the Svelte UI library, offering routing, server-side rendering, and deployment tooling.
E. Next.js
Next.js is a popular React-based framework for building server-rendered and statically generated web applications with features like routing, API routes, and performance optimizations built in.
F. None of above. chosen

Statements (48)

Predicate	Object
instanceOf	.NET web framework ⓘ single-page application framework ⓘ web framework ⓘ
deploymentModel	Blazor self-linksurface differs ⓘ surface form: Blazor Hybrid Blazor self-linksurface differs ⓘ surface form: Blazor Server Blazor self-linksurface differs ⓘ surface form: Blazor United (ASP.NET Core full-stack UI) Blazor self-linksurface differs ⓘ surface form: Blazor WebAssembly
developer	Microsoft ⓘ
documentation	https://learn.microsoft.com/aspnet/core/blazor ⓘ
enables	building interactive client-side web UIs ⓘ
firstPublicPreviewYear	2018 ⓘ
integratesWith	dotnet/aspnetcore ⓘ surface form: ASP.NET Core SignalR (for Blazor Server real-time updates) ⓘ
introducedBy	Microsoft .NET team ⓘ surface form: .NET Core team at Microsoft
license	proprietary with open-source components ⓘ
partOf	.NET ecosystem ⓘ surface form: .NET platform
platform	.NET Framework ⓘ surface form: .NET
programmingLanguage	C# programming language ⓘ surface form: C#
replaces	JavaScript for client-side UI logic in many scenarios ⓘ
repository	https://github.com/dotnet/aspnetcore ⓘ
runsOn	.NET runtime ⓘ WebAssembly specification ⓘ surface form: WebAssembly web browser ⓘ web server ⓘ
stableReleaseIncludedIn	.NET Core ⓘ surface form: .NET Core 3.0
supports	CSS isolation for components ⓘ JavaScript interop ⓘ Razor syntax ⓘ authentication and authorization via ASP.NET Core Identity ⓘ component libraries ⓘ component-based UI development ⓘ data binding ⓘ dependency injection ⓘ event handling ⓘ form validation ⓘ full-stack web development with .NET ⓘ hot reload for .NET code ⓘ interactive client-side components ⓘ interactive server-side components ⓘ layout components ⓘ model-view-component style architecture ⓘ prerendering in ASP.NET Core ⓘ progressive web apps via WebAssembly ⓘ routing ⓘ server-side rendering ⓘ two-way data binding via @bind ⓘ
targetAudience	.NET developers building web applications ⓘ
uses	Razor components ⓘ

How these facts were elicited

Referenced by (10)

Full triples — surface form annotated when it differs from this entity's canonical label.

ASP.NET → includesComponent → Blazor ⓘ

Rider → supportsTechnology → Blazor ⓘ

Microsoft .NET documentation → topic → Blazor ⓘ

Blazor → deploymentModel → Blazor self-linksurface differs ⓘ

this entity surface form: Blazor Server

Blazor → deploymentModel → Blazor self-linksurface differs ⓘ

this entity surface form: Blazor WebAssembly

Blazor → deploymentModel → Blazor self-linksurface differs ⓘ

this entity surface form: Blazor Hybrid

Blazor → deploymentModel → Blazor self-linksurface differs ⓘ

this entity surface form: Blazor United (ASP.NET Core full-stack UI)

.NET MAUI → integratesWith → Blazor ⓘ

this entity surface form: ASP.NET Core Blazor

.NET ecosystem → includesComponent → Blazor ⓘ

JetBrains Rider → supportsTechnology → Blazor ⓘ

All labels observed (6)

How this entity was disambiguated Show

Statements (48)

How these facts were elicited Show

Referenced by (10)

How this entity was disambiguated

How these facts were elicited