What's the alternative to runtime compilation if it will be no longer supported?

[gitPhate]

I read the Runtime Compilation section of the README of this project, in particular:

If you're looking to save a Razor view in a database or in a separate folder outside the project and render it on the fly, that scenario is not supported

But I'm wondering what's the alternative? Isn't it the goal of this library to render a Razor view at runtime? Is it possible to compile it?

[soundaranbu]

Hey @gitPhate, Runtime compilation is not possible with this library unfortunately as it's not the main goal. Instead it is to render the views that are already precompiled as part of building/publishing your project.

In the README:

This library uses precompiled Razor views provided by the Razor SDK.

Before .NET 10, it was indeed possible to do runtime compilation using Microsoft.AspNetCore.Mvc.Razor.RuntimeCompilation nuget package (original purpose was to do hot reload during development) along with the Razor.Templating.Core package. But, Microsoft made the RuntimeCompilation package obsolete. You can read more about the announcement and the reason here. So, there's no officially supported package for Runtime compilation going forward.

If Runtime Compilation is a mandatory requirement for your usecase, then I would point you to packages like RazorLight, which looks to support those scenarios. If I come across any other library, I'll add them here.

Happy to discuss further, if there are any more questions. Thanks.

[gitPhate]

I found this library: https://github.com/adoconnection/RazorEngineCore which appears to compile templates directly. This is an LLM analysis:

RazorEngineCore is not affected by this deprecation. Here's why:
The Microsoft deprecation targets a specific set of ASP.NET Core MVC APIs — namely AddRazorRuntimeCompilation and related types in the Microsoft.AspNetCore.Mvc.Razor.RuntimeCompilation namespace. These APIs allowed .cshtml view files to be recompiled while an MVC application was running, without a restart.
RazorEngineCore takes a fundamentally different approach. It doesn't hook into the ASP.NET Core MVC pipeline at all. Instead, it uses Microsoft.AspNetCore.Razor.Language (the Razor compiler) and Microsoft.CodeAnalysis.CSharp (Roslyn) directly to compile Razor string templates into in-memory assemblies. None of the deprecated APIs (AddRazorRuntimeCompilation, FileProviderRazorProjectItem, MvcRazorRuntimeCompilationOptions, etc.) appear anywhere in its codebase.

It should be good for my use case.
Many thanks!