133eff3119
- Instead of using Razor/Mvc TemplateEngine use `RazorProjectEngine`. This involved changing several locations (each of which used `RazorTemplateEngine` in an entirely different way) to use the RazorProjectEngine's two Process methods. - Changed an unused public API `VisualStudioRazorParser.TemplateEngine` to `VisualStudioRazorParser.RazorProjectEngine`. - Ported the remainder of `RazorEngineBuilder`'s extension methods over to `RazorProjectEngineBuilder`. These were used in tests and our `RazorGenerate` tool. - Added a few test helper methods/classes to enable simple testing of the `RazorProjectEngine`. - Resolved several test hacks that were working around little discrepancies each of the `RazorTemplateEngine` APIs. - Changed the template engine factory service to be a project engine factory service. |
||
|---|---|---|
| .. | ||
| AssemblyInfo.cs | ||
| CodeGenerationBenchmark.cs | ||
| MSN.cshtml | ||
| Microsoft.AspNetCore.Razor.Performance.csproj | ||
| TagHelperSerializationBenchmark.cs | ||
| readme.md | ||
| taghelpers.json | ||
readme.md
Compile the solution in Release mode (so binaries are available in release)
To run a specific benchmark add it as parameter.
dotnet run -c Release <benchmark_name>
If you run without any parameters, you'll be offered the list of all benchmarks and get to choose.
dotnet run -c Release