Go to file
Ryan Nowak 7cc90e48c0 Fix a few authoring errors with VSIX 2018-02-26 12:16:14 -08:00
build
samples Set IsPackable=false on certain projects 2018-02-26 15:27:57 +00:00
src Include "serve" command in dotnet-blazor tool 2018-02-26 17:37:00 +00:00
test Support @bind for textboxes and checkboxes 2018-02-26 14:39:56 +00:00
tooling Fix a few authoring errors with VSIX 2018-02-26 12:16:14 -08:00
.appveyor.yml Workaround AppVeyor failing to install Chrome 2018-02-23 10:38:52 +00:00
.gitignore Configure output path for "dotnet pack" 2018-02-26 15:20:23 +00:00
.travis.yml
Blazor.sln Add an example API server project that can be used in E2E tests 2018-02-23 13:07:49 +00:00
BlazorTooling.sln
CODE_OF_CONDUCT.md
CONTRIBUTING.md
Directory.Build.props Configure output path for "dotnet pack" 2018-02-26 15:20:23 +00:00
LICENSE.txt
README.md
THIRD-PARTY-NOTICES.txt
nuget.config
version.props Add build version config 2018-02-26 15:13:36 +00:00

README.md

Blazor

An experimental web UI framework using C#/Razor and HTML, running in the browser via WebAssembly

Gitter

Blazor is a .NET web framework that runs in any browser. You author Blazor apps using C#/Razor and HTML.

Blazor uses only the latest web standards. No plugins or transpilation needed. It runs in the browser on a real .NET runtime (Mono) implemented in WebAssembly that executes normal .NET assemblies. It works in older browsers too by falling back to an asm.js based .NET runtime.

Blazor will have all the features of a modern web framework, including:

  • A component model for building composable UI
  • Routing
  • Layouts
  • Forms and validation
  • Dependency injection
  • JavaScript interop
  • Live reloading in the browser during development
  • Server-side rendering
  • Full .NET debugging both in browsers and in the IDE
  • Rich IntelliSense and tooling
  • Ability to run on older (non-WebAssembly) browsers via asm.js
  • Publishing and app size trimming

Note: Blazor is an experimental project. It's not (yet) a committed product. This is to allow time to fully investigate the technical issues associated with running .NET in the browser and to ensure we can build something that developers love and can be productive with. During this experimental phase, we expect to engage deeply with early Blazor adopters like you to hear your feedback and suggestions.

To see Blazor in action, check out Steve Sanderson's prototype demo at NDC Oslo last year. You can also try out a simple live Blazor app.

Getting Started

We are still very early in this project. There isn't yet anything you can download nor any project template you can use. Most of the planned features aren't implemented yet. Even the parts that are already implemented aren't yet optimized for minimal payload size. If you're keen, you can clone the repo, build it, and run the samples and tests.

Build

Prerequisites:

Run dotnet build Blazor.sln from the solution directory.

Run tests

Run dotnet test test/<dir>/<project>.Test.csproj

Run end-to-end tests

Prerequisites:

  • Install selenium-standalone (requires Java 8 or later)
    • npm install -g selenium-standalone
    • selenium-standalone install
  • Chrome

Run selenium-standalone start

Run dotnet test test\Microsoft.AspNetCore.Blazor.E2ETest\Microsoft.AspNetCore.Blazor.E2ETest.csproj

Run all tests

Install prerequisites for E2E tests

Run dotnet test test\AllTests.proj

Contributing

There are lots of ways that you can contribute to Blazor! Read our contributing guide to learn about our development process and how to propose bug fixes and improvements.

Still got questions?

Check out our FAQ or open an issue.