03dea86c4e
I noticed we were really undertesting all of the things that handle paths and file names. I gave this some love and a little clean up where we weren't doing the right thing in RazorSourceDocument. Also changed the template engine tests to use the FileSystemRazorProject. These tests are already using the files on disk as inputs. I turned off checksums for these since they now have the full file path, and that would not be portable. |
||
|---|---|---|
| benchmarks/Microsoft.AspNetCore.Razor.Performance | ||
| build | ||
| shared/Microsoft.AspNetCore.Razor.TagHelpers.Testing.Sources | ||
| src | ||
| test | ||
| tooling | ||
| .appveyor.yml | ||
| .editorconfig | ||
| .gitattributes | ||
| .gitignore | ||
| .travis.yml | ||
| CONTRIBUTING.md | ||
| Directory.Build.props | ||
| Directory.Build.targets | ||
| LICENSE.txt | ||
| NuGet.config | ||
| NuGetPackageVerifier.json | ||
| README.md | ||
| Razor.sln | ||
| build.cmd | ||
| build.sh | ||
| korebuild-lock.txt | ||
| korebuild.json | ||
| run.cmd | ||
| run.ps1 | ||
| run.sh | ||
| version.props | ||
README.md
Razor
AppVeyor:
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.