Now that IRazorComponentApplication<T> is removed, what is the replacement to discover endpoint for Blazor SSR?

[dodyg]

https://github.com/dotnet/aspnetcore/pull/48283/files#diff-a7f3c6db39f6146badbd23e53b266014ab84a78b73e26998961b2f1ab62ce32f

My simple sample for SSR no longer works using Preview 6

https://github.com/dodyg/practical-aspnetcore/blob/net6.0/projects/.net8/RazorComponentOne/README.md

[gfoidl]

Did you see #46980 (comment)?
(Note: this is not my domain, so I hope to gave you the right pointer)

[dodyg]

Yeah I have read those. It doesn't have any useful specific unfortunately.

[gfoidl]

@javiercn please shed some light into this question.

[javiercn]

We got rid of the interface, we are working on a mechanism that is based on source generation, but the public entry point for any of this is MapRazorComponents() that exposes a ComponentApplicationBuilder instance

[javiercn]

Is there a concrete scenario you are trying to achieve?

[dodyg]

I just want the following code to work

var builder = WebApplication.CreateBuilder();
builder.Services.AddRazorComponents();

var app = builder.Build();

app.MapRazorComponents<RazorComponentOne.Shared.MainLayout>();

app.Run();

@page "/"

Good morning hello world

<Greetings Message="Hello World" />

[javiercn]

@dodyg put an App component and add a router inside, exactly how you would do in Blazor Server or Web assembly.

[dodyg]

@javiercn I added the App.razor and now the layout renders. However the body of the layout doesn't.