Blazor is an experimental .NET web framework using C#/Razor and HTML that runs in the browser with WebAssembly
C# TypeScript C Shell PowerShell CSS Other
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Failed to load latest commit information.
benchmarks/Microsoft.AspNetCore.Blazor.Performance Add support for conditional attributes Apr 3, 2018
build Update Korebuild May 22, 2018
samples Simple autorebuild mechanism for hosted apps (#787) May 22, 2018
src Handle ChildContent that starts with an HTML element. Fixes #875 May 23, 2018
test Handle ChildContent that starts with an HTML element. Fixes #875 May 23, 2018
tooling Refactor VS references May 22, 2018
.appveyor.yml Update version numbers to 0.2 in preparation for 0.2 Apr 11, 2018
.editorconfig Event payloads for DOM event types May 22, 2018
.gitattributes Fix line endings on OSX Apr 18, 2018
.gitignore Add support for conditional attributes Apr 3, 2018
.travis.yml Update version numbers to 0.2 in preparation for 0.2 Apr 11, 2018
Blazor.sln Encourage encapsulation of component parameter properties (#713) May 1, 2018
CODE_OF_CONDUCT.md Add contributing guide and code of conduct Jan 30, 2018
CONTRIBUTING.md Remove extra apostrophe Apr 16, 2018
Directory.Build.props Update ASP.NET Core dependencies to RC May 22, 2018
Directory.Build.targets Konvert to KoreBuild Mar 14, 2018
LICENSE.txt Add LICENSE.txt Jan 27, 2018
README.md Update ASP.NET Core dependencies to RC May 22, 2018
THIRD-PARTY-NOTICES.txt Bootstrap 4 and new styling (#619) Apr 19, 2018
build.cmd Konvert to KoreBuild Mar 14, 2018
build.sh Konvert to KoreBuild Mar 14, 2018
global.json Update Korebuild May 22, 2018
korebuild-lock.txt Update Korebuild May 22, 2018
korebuild.json Update Korebuild May 22, 2018
run.cmd Konvert to KoreBuild Mar 14, 2018
run.ps1 Konvert to KoreBuild Mar 14, 2018
run.sh Konvert to KoreBuild Mar 14, 2018
version.props Update binding redirection version range for 0.4.0 May 1, 2018

README.md

Blazor

An experimental .NET web framework using C#/Razor and HTML that runs 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

To get started with Blazor and build your first Blazor web app check out our getting started guide.

Building the Repo

Prerequisites:

The Blazor repository uses the same set of build tools as the other ASP.NET Core projects. The developer documentation for building is the authoritative guide. Please read this document and check your PATH setup if you have trouble building or using Visual Studio

To build at the command line, run build.cmd or build.sh from the solution directory.

Run unit tests

Run build.cmd /t:Test or build.sh /t:Test

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 build.cmd /t:Test /p:BlazorAllTests=true or build.sh /t:Test /p:BlazorAllTests=true

Opening in Visual Studio

Prerequisites:

  • Follow the steps here to set up a local copy of dotnet
  • Visual Studio 2017 15.7 latest preview - download

We recommend getting the latest preview version of Visual Studio and updating it frequently. The Blazor editing experience in Visual Studio depends on new features of the Razor language tooling and will be updated frequently.

When installing Visual Studio choose the following workloads:

  • ASP.NET and Web Development
  • Visual Studio extension development features

If you have problems using Visual Studio with Blazor.sln please refer to the developer documentation.

Developing the Blazor VS Tooling

To do local development of the Blazor tooling experience in VS, select the Microsoft.VisualStudio.BlazorExtension project and launch the debugger.

The Blazor Visual Studio tooling will build as part of the command line build when on Windows.

Using CI Builds of Blazor

To use a nightly or developer CI build of the Blazor package, ensure that you have the Blazor package feed configured, and update your package version numbers. You should use developer builds only with the expectation that things will break and change without any sort of announcement.

Update your projects to include the Blazor developer feed (https://dotnet.myget.org/f/blazor-dev/api/v3/index.json) and ASP.NET Core developer feed (https://dotnet.myget.org/F/dotnet-core/api/v3/index.json). You can do this in a project file with MSBuild:

<RestoreSources>
    $(RestoreSources);
    https://api.nuget.org/v3/index.json;
    https://dotnet.myget.org/F/dotnet-core/api/v3/index.json;
    https://dotnet.myget.org/f/blazor-dev/api/v3/index.json;
</RestoreSources>

Or in a NuGet.config in the same directory as the solution file:

<?xml version="1.0" encoding="utf-8"?>
<configuration>
 <packageSources>
    <clear />
    <add key="blazor" value="https://dotnet.myget.org/f/blazor-dev/api/v3/index.json" />
    <add key="aspnet" value="https://dotnet.myget.org/f/dotnet-core/api/v3/index.json" />
    <add key="nuget" value="https://api.nuget.org/v3/index.json" />
 </packageSources>
</configuration>

You can browse https://dotnet.myget.org/gallery/blazor-dev to find the current versions of packages. We recommend picking a specific version of the packages and using it across your projects.

<ItemGroup>
    <PackageReference Include="Microsoft.AspNetCore.Blazor.Browser" Version="0.3.0-preview1-10220" />
    <PackageReference Include="Microsoft.AspNetCore.Blazor.Build" Version="0.3.0-preview1-10220" />
    <DotNetCliToolReference Include="Microsoft.AspNetCore.Blazor.Cli" Version="0.3.0-preview1-10220" />
</ItemGroup>

To install a developer CI build of the Blazor Language Service extension for Visual Studio, add https://dotnet.myget.org/F/blazor-dev/vsix/ as an additional extension gallery by going to Tools -> Options -> Environment -> Extensions and Updates:

image

You should then be able to install or update the Blazor Language Service extension from the developer CI feed using the Extensions and Updates dialog.

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.