Step 1: Add HostProject This is a somewhat complex addition to the ProjectSnapshotManager. Now that we accept updates from the underlying IDE project system we need to coordinate those with the Workspace. This means that ProjectSnapshot itself now also has a version concept. Step 2: Introduce a new project system based on CPS We use project capabilities defined by the Razor SDK to determine whether to rely on MSBuild evaluation to detect the configuration or whether to fallback to assembly-based detection. Step 3: Flow RazorConfiguration everywhere We use now expose the RazorConfiguration to the language service and editor. This means that we no longer need to detect the project's configuration asynchronously, it happens much faster now. |
||
|---|---|---|
| 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
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.