Blazor is a single-page web application (SPA) framework built on .NET that runs in the browser with Mono's WebAssembly run-time, or server-side via SignalR. Blazor features a component architecture, routing, a virtual DOM, and a JavaScript Interoperability (interop) API. Currently, Blazor is in an experimental state which allows for rapid development, iterations, and as implied, experimentation.
9. C#/Razor + HTML
Blazor is an experimental .NET web
framework using C# and HTML that runs in
the browser.
Browser + Razor = Blazor
10. Just the FAQs
What it is
• Client Side C#
• Web Standard Technologies
• WebAssembly
• .NET Standard
• Experimental
What it’s NOT
• A Plugin
• ASP.NET WebForms
• Trans-piled JavaScript
13. WebAssembly (wasm)
WebAssembly is a web standard that defines
an assembly-like format for executable code
in Web pages.
It’s what makes Blazor possible.
23. Prerequisites
• .NET Core 2.1 SDK (2.1.300 or later).
• Visual Studio 2017 15.7
• Blazor Language Services extension from the Visual
Studio Marketplace.
31. Ed Charbeneau
Developer Advocate for Progress<Telerik>
Author<T>
Podcast => “Eat Sleep Code”
Twitter.Where(user == @EdCharbeneau)
Editor's Notes
Subject to change, break, and be cancelled
WebForms tried to be stateful web
Silverlight didn’t conform to web standards
Even if your not a .NET Developer, this is exciting
Parser creates a syntax tree
Syntax tree compiles to byte code
Bytecode is executed by the interpreter at runtime
Unlike TypeScript, WebAssembly code is actually compiled byte code
This allows us to build JavaScript byte code with other languages
Inversion of control
Blazor is a UI framework
It relies on the Mono WebAssembly Runtime
Our apps are not compiled directly to WebAssembly
Blazor.js and Mono.js marshal calls between JavaScript and C#