Blazor is an experimental .NET web framework using C#/Razor and HTML that runs in the browser with WebAssembly
Clone or download
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.azure In Azure build pipeline, ensure we have the expected version of Node Nov 26, 2018
build Clean up after mondorepo migration (#1734) Nov 29, 2018
modules Update to latest JSInterop Oct 10, 2018
src Simplify how .Mono project depends on .BuildTools (#1760) Dec 11, 2018
.editorconfig Automate authenticode code-signing using Roslyn sign tool Aug 8, 2018
.gitattributes Fix line endings on OSX Apr 18, 2018
.gitignore Clean up after mondorepo migration (#1734) Nov 29, 2018
.gitmodules Consume jsinterop from submodule (#1351) Aug 29, 2018
Blazor.sln Clean up after mondorepo migration (#1734) Nov 29, 2018
CODE_OF_CONDUCT.md Add contributing guide and code of conduct Jan 30, 2018
CONTRIBUTING.md Clean up after mondorepo migration (#1734) Nov 29, 2018
Directory.Build.props Clean up after mondorepo migration (#1734) Nov 29, 2018
Directory.Build.targets Konvert to KoreBuild Mar 14, 2018
LICENSE.txt Add LICENSE.txt Jan 27, 2018
README.md Clean up after mondorepo migration (#1734) Nov 29, 2018
THIRD-PARTY-NOTICES.txt TextDecoder polyfill (#1168) Jul 23, 2018
build.cmd Konvert to KoreBuild Mar 14, 2018
build.sh Konvert to KoreBuild Mar 14, 2018
global.json Upgrade KoreBuild (#1498) Oct 1, 2018
korebuild-lock.txt Upgrade KoreBuild (#1498) Oct 1, 2018
korebuild.json Upgrade KoreBuild (#1498) Oct 1, 2018
nuget.config Clean up after mondorepo migration (#1734) Nov 29, 2018
run.cmd Konvert to KoreBuild Mar 14, 2018
run.ps1 Update KoreBuild and bootstrappers Aug 3, 2018
run.sh Update KoreBuild and bootstrappers Aug 3, 2018
version.props Clean up after mondorepo migration (#1734) Nov 29, 2018

README.md

Blazor

For information about using Blazor, see blazor.net.

Sources moved

Almost all the sources for Blazor and the Razor Components programming model have moved here in the central ASP.NET Core repo. We are also in the process of migrating open issues from here to there.

This is in preparation for shipping Razor Components as a built-in feature of ASP.NET Core 3.0. Note: client-side Blazor remains experimental while we continue to work on making the WebAssembly runtime complete.

Where should I post issues and PRs now?

New issues and PRs should be posted at the central ASP.NET Core repo.

Please don't post new issues or PRs in this repo.

What about the existing outstanding PRs in this repo?

Currently you don't need to do anything. Soon we will address each of the outstanding PRs on a case-by-case basis. In many cases we will ask the author to consider migrating their PR to the new repo and can provide guidance on that. In some cases we may think the PR is no longer applicable.

We apologize for the extra work this involves. This move had to happen at some point in order for the technology to ship.