Go to file
Ryan Nowak e8af1141cb Attempt to fix Razor CI flakiness
We're seeing some test failures on the CI where the build has no output.
Sure enough, using Process.Exited is trap. It doesn't guarantee that all
of the output has been written when it's trigger.

This is a different approach that shouldn't suffer from the same
problem.
2018-01-16 17:18:44 -08:00
benchmarks/Microsoft.AspNetCore.Razor.Performance
…
build Update deps 2018-01-16 12:41:21 -08:00
shared/Microsoft.AspNetCore.Razor.TagHelpers.Testing.Sources
…
src Make Razor SDK support refs and views on publish 2018-01-14 11:43:01 -08:00
test Attempt to fix Razor CI flakiness 2018-01-16 17:18:44 -08:00
tooling
…
.appveyor.yml Update bootstrappers 2017-10-09 12:45:14 -07:00
.editorconfig
…
.gitattributes
…
.gitignore
…
.travis.yml
…
CONTRIBUTING.md
…
Directory.Build.props
…
Directory.Build.targets
…
LICENSE.txt
…
NuGet.config
…
NuGetPackageVerifier.json Update build tools to 2.1.0-preview1-15670 and update list of exclusions for Razor.Design 2018-01-12 14:29:59 -08:00
README.md
…
Razor.sln Unify how AdhocWorkspace is constructed. 2018-01-12 17:54:53 -08:00
build.cmd
…
build.sh
…
korebuild-lock.txt Update deps 2018-01-16 12:41:21 -08:00
korebuild.json
…
run.cmd
…
run.ps1
…
run.sh
…
version.props
…

README.md

Razor

AppVeyor: AppVeyor

Travis: Travis

The Razor syntax provides a fast, terse, clean and lightweight way to combine server code with HTML to create dynamic web content. This repo contains the parser and the C# code generator for the Razor syntax.

This project is part of ASP.NET Core. You can find samples, documentation and getting started instructions for ASP.NET Core at the Home repo.

Building from source

To run a complete build on command line only, execute build.cmd or build.sh without arguments. See developer documentation for more details.