Split Area for pages

[Alerinos]

Is there an existing issue for this?

• I have searched the existing issues

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

Many systems like mine have Areas.
Let's assume that in my case it looks like this:

• Web, this is an area available to anyone
• Manage, this is the area available to the logged in person
• Management, this is an area available only to administration.

This is how my plugin tree looks like:

├───Areas
│   ├───Manage
│   │   │   _Imports.razor
│   │   │
│   │   └───Pages
│   │           Edit.razor
│   │           Edit.razor.cs
│   │           List.razor
│   │           List.razor.cs
│   │
│   ├───Management
│   │   │   _Imports.razor
│   │   │
│   │   └───Pages
│   │           Draft.razor
│   │           Draft.razor.cs
│   │           Edit.razor
│   │           Edit.razor.cs
│   │           List.razor
│   │           List.razor.cs
│   │
│   └───Web
│       │   _Imports.razor
│       │
│       ├───Pages
│       │       Article.razor
│       │       Article.razor.cs
│       │       Articles.razor
│       │       Articles.razor.cs
│       │       Search.razor
│       │       Search.razor.cs
│       │
│       └───Shared
│               ArticleCardCaption.razor
│               ArticleHead.razor
│               ArticlePopular.razor

You used to be able to separate everything into arenas that were separated, they could have their App.razor and Routing.razor.
Now it's all lumped into one ``bag''.

endpoints.MapRazorComponents<Areas.Web.App>()
                    .AddInteractiveServerRenderMode()
                    .AddInteractiveWebAssemblyRenderMode()
                    .AddAdditionalAssemblies(assemblyWeb);

endpoints.MapRazorComponents<Areas.Manager.App>()
                    .AddInteractiveServerRenderMode()
                    .AddInteractiveWebAssemblyRenderMode()
                    .AddAdditionalAssemblies(assemblyManager);

endpoints.MapRazorComponents<Areas.Management.App>()
                    .AddInteractiveServerRenderMode()
                    .AddInteractiveWebAssemblyRenderMode()
                    .AddAdditionalAssemblies(assemblyManagement);

It is now possible to solve this problem but only by creating a solucja (we are coming up with three more solucja). I think this is a bad solution and we need to have an impact on which pages should appear in routing.

If we add a component in AdditionalAssemblies it finds all other components from a given soluition. Instead of taking the Assmelby parameter, you can change it to Type[], then we can indicate the exact location of the component in question

Describe the solution you'd like

I would like it to be possible to indicate exactly the components to be under a given routing. He wants to separate everything. Each area has different values.

Additional context

No response

[mkArtakMSFT]

Thanks for contacting us. Have you considered separating these areas using the MapWhen extension method? https://learn.microsoft.com/aspnet/core/fundamentals/middleware/?view=aspnetcore-7.0#branch-the-middleware-pipeline

Hi @Alerinos. We have added the "Needs: Author Feedback" label to this issue, which indicates that we have an open question for you before we can take further action. This issue will be closed automatically in 7 days if we do not hear back from you by then - please feel free to re-open it if you come back to this issue after that time.

[Alerinos]

@mkArtakMSFT Yes, this is my code. Despite using MapWhen, the problem still occurs.

    public static IApplicationBuilder UseManager(this WebApplication builder)
    {
        builder.MapWhen(ctx => ctx.Request.Path.StartsWithSegments("/manager"), app =>
        {
            app.UsePathBase("/manager/");
            app.UseStaticFiles();
            app.UseRouting();
            app.UseAntiforgery();

            //app.UseEndpoints(endpoints =>
            //{
            //    var assembly = AssemblyProvider.Types<IAreaManager>().ToArray();

            //    endpoints.MapControllers();
            //    endpoints.MapRazorComponents<Areas.Manager.App>()
            //        .AddInteractiveServerRenderMode()
            //        .AddInteractiveWebAssemblyRenderMode()
            //        .AddAdditionalAssemblies(assembly);
            //});

            app.UseEndpoints(endpoints =>
            {
                endpoints.MapControllers();
                endpoints.MapBlazorHub("/_blazor");
                endpoints.MapFallbackToAreaPage("/{*clientroutes:nonfile}", "/_Host", "Manager");
            });
        });

        return builder;
    }

I spent a lot of time debugging and looking for a solution. Assembly always returns us a solution, in this case a DLL. It seems to me that the recent changes in .net 8 introduced the use of all components that contain @page.
As far as I remember, in .net 7 there was no such problem

[javiercn]

@mkArtakMSFT this is a request for customizable discovery like MVC has. We scoped this out of 8.0

Thanks for contacting us.

We're moving this issue to the .NET 9 Planning milestone for future evaluation / consideration. We would like to keep this around to collect more feedback, which can help us with prioritizing this work. We will re-evaluate this issue, during our next planning meeting(s).
If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues.
To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

[Alerinos]

@javiercn @mkArtakMSFT

I consider this problem critical, I had authorization of the entire arena in App.razor and MainLayout.razor. If my sub-sites are allowed to run in another Area it causes a security breach (For example, in one that has no authorization). I have now added authorization attributes to each page so I have fixed the problem, I'm afraid others like me may have had the same.

Example MainLayout.razor:

<AuthorizeView Policy="AllowManagement">
    <Authorized>
        @Body
    </Authorized>

    <NotAuthorized>
        Log in...
    </NotAuthorized>
</AuthorizeView>