[Feature request] support to use blazor razor as template engine to render report and save the raw string

[congzhangzh]

Is your feature request related to a problem? Please describe.

Hope blazor razor can be use as a template render tools to render report, I use C# interpolate string、 JavaScript interpolate string、 Python Jinja2 to generator report before.

But razor for blazor is more powerful, as all the template language just support express embedded and with some type of directives to do control flow, which is very limit and a free form like Blazor/PHP/JSP is more welcome.

So, if razor flor blazor can be use standalone or with minimum env setup, it will be a great to to do report generation tools development like.

razor component(RazorRenderComponent)

<table>
@for(var case in doc.Select('/testcase')
{
   <tr> <td>@case.Attribute["Name"]</td> <td>@case.Attribute["passed"]</td></tr>
}
</table>
@code{

public    XDocument doc;
}

main program

int Main(string[] args)
{
var render=new RazorRenderComponent()
render.doc=XDocument.Load('junit.xml')
var result=render.render();
System.Console.WriteLine(result);
}

Describe the solution you'd like

Please consider provider a simple api to render result to string, and minimum the context init process, like DI

Additional context

Blazor's free form render process is really cool, support statement and no need special and limited directives to do flow control, it will make report generator funcation easy to develop or release as an standalone program.

[congzhangzh]

@shanselman how do you think about this idea?

BTW, blazor syntax is really easy than some type of react syntax, free form of for loop is better than some type of map in react.

[congzhangzh]

@mkArtakMSFT BTW, razor & blazor use the same template engine?

[ghost]

We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process.

[mkArtakMSFT]

This is addressed by: #46935
You can find a sample code for how to use the new API for a templating engine scenario in our preview release announcement blog post: https://devblogs.microsoft.com/dotnet/asp-net-core-updates-in-dotnet-8-preview-3/ (look for Render Razor components outside of ASP.NET Core section)

@guardrex I checked the docs and it seems that the writeup you added for that PR didn't actually include the templating engine scenario. I think it should as this comes up quite often. Can you please expand that writeup to cover the templating engine scenario.

[guardrex]

@mkArtakMSFT ... I don't think that's the right spot. Can you see if it's completely covered here? ...

https://learn.microsoft.com/en-us/aspnet/core/blazor/components/render-components-outside-of-aspnetcore?view=aspnetcore-8.0