874050f1dd
* Add Ignitor * Finish headless Blazor client. * Added support for click events. * Move Ignitor into testassets folder. - Also added Ignitor to the no deps solution. * Add Ignitor tests to validate RenderBatchReader stays consistent. |
||
|---|---|---|
| .. | ||
| Analyzers | ||
| Blazor | ||
| Browser | ||
| Browser.JS | ||
| Components | ||
| Server | ||
| Shared | ||
| test | ||
| Components.sln | ||
| ComponentsNoDeps.slnf | ||
| Directory.Build.props | ||
| Directory.Build.targets | ||
| NuGetPackageVerifier.json | ||
| README.md | ||
| THIRD-PARTY-NOTICES.txt | ||
| build.cmd | ||
| build.sh | ||
| startvs.cmd | ||
README.md
Blazor
Build modern, interactive web-based UIs with C# and Razor.
This folder contains the underlying components programming model that powers both server-side and client-side Blazor applications.
Blazor is a component based web UI framework. Blazor apps can run client-side in browser on WebAssembly or server-side as part of an ASP.NET Core app. Blazor is a full single-page application (SPA) framework inspired by the latest JavaScript SPA frameworks, featuring support for offline/PWA applications, app size trimming, and browser-based debugging.
Blazor uses only the latest web standards. No plugins or transpilation needed. It runs in the browser on a real .NET runtime implemented in WebAssembly that executes normal .NET assemblies.
You can learn more about Blazor at https://blazor.net.
Getting Started
To get started with Blazor and build your first web app check out our getting started guide.