Migrate AdminPanel and MapApp from Blazor Server App to Blazor Web App

[Copilot]

Migration Plan: Blazor Server App to Blazor Web App ✅

• Explore repository structure and understand current implementation
• Update WebApplicationExtensions.cs in AdminPanel to use new Blazor Web App APIs
• Update WebApplicationExtensions.cs in MapApp to use new Blazor Web App APIs
• Update App.razor files to include full HTML document structure
• Update AdminPanel.Host Program.cs to use new routing
• Update GameServer.Host Program.cs to use new routing
• Update Dapr/Common/Extensions.cs ConfigureDaprService method
• Update MapApp.cs (obsolete) to use new Blazor Web App pattern
• Update Startup.cs to use new Blazor Web App pattern
• Build and test the changes
• Remove old _Host.cshtml and _Layout.cshtml files
• Run code review and address feedback
• Run security scanning
• Fix static asset path resolution issues (part 1)
• Fix static asset serving for NuGet package dependencies (in progress)

Current Issue

The static web assets from NuGet packages (Blazored.Modal, Blazored.Toast, etc.) are returning 404 errors. Investigation shows:

• AdminPanel's static web assets manifest includes the Blazored packages correctly
• The Startup project doesn't generate its own consolidated manifest
• The FixNetSdkDiscoverAssetsBug workaround in csproj files may be interfering

Working on solution to ensure NuGet package assets are served correctly from host applications.

Build Status: ✅ Passing

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Migrate AdminPanel and MapApp from 'Blazor Server App' to 'Blazor Web App'</issue_title>
<issue_description>Is your feature request related to a problem? Please describe.
The AdminPanel structure and initialization must be modernized to be able to use new blazor features.
The AdminPanel project and depending web projects need to be migrated to the new way of doing blazor applications. It feels like some new and old features are mixed in the current codebase and it's very confusing to work with it.
The required steps are at: https://learn.microsoft.com/en-us/aspnet/core/migration/80-to-90?view=aspnetcore-8.0&tabs=visual-studio

Describe the solution you'd like
Following the guide, the AdminPanel needs to be adapted, so it's based upon an 'App.razor' file instead of '_Host.cshtml' and '_Layout.cshtml'.

The orchestration of the application must be adapted in the following locations:

• MUnique.OpenMU.Web.AdminPanel.WebApplicationExtensions
• MUnique.OpenMU.Web.AdminPanel.Host.Program
• MUnique.OpenMU.Web.GameServer.Host.Program

Additional context
To have a clean reference project, start a new project 'Blazor Web App' in Visual Studio 2026.
E.g. new:

using BlazorWebApp.Components;

var builder = WebApplication.CreateBuilder(args);

// Add services to the container.
builder.Services.AddRazorComponents()
    .AddInteractiveServerComponents();

var app = builder.Build();

// Configure the HTTP request pipeline.
if (!app.Environment.IsDevelopment())
{
    app.UseExceptionHandler("/Error", createScopeForErrors: true);
    // The default HSTS value is 30 days. You may want to change this for production scenarios, see https://aka.ms/aspnetcore-hsts.
    app.UseHsts();
}
app.UseStatusCodePagesWithReExecute("/not-found", createScopeForStatusCodePages: true);
app.UseHttpsRedirection();

app.UseAntiforgery();

app.MapStaticAssets();
app.MapRazorComponents<App>()
    .AddInteractiveServerRenderMode();

app.Run();

old:

using BlazorServerApp_Old.Data;
using Microsoft.AspNetCore.Components;
using Microsoft.AspNetCore.Components.Web;

var builder = WebApplication.CreateBuilder(args);

// Add services to the container.
builder.Services.AddRazorPages();
builder.Services.AddServerSideBlazor();

var app = builder.Build();

// Configure the HTTP request pipeline.
if (!app.Environment.IsDevelopment())
{
    app.UseExceptionHandler("/Error");
    // The default HSTS value is 30 days. You may want to change this for production scenarios, see https://aka.ms/aspnetcore-hsts.
    app.UseHsts();
}

app.UseHttpsRedirection();

app.UseStaticFiles();

app.UseRouting();

app.MapBlazorHub();
app.MapFallbackToPage("/_Host");

app.Run();

```</issue_description>

## Comments on the Issue (you are @copilot in this section)

<comments>
</comments>

• Fixes Migrate AdminPanel and MapApp from 'Blazor Server App' to 'Blazor Web App' #675

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[sven-n]

It does not work yet. I started the Startup project and opened the admin panel in the browser. It can't get some static web assets:

GET
http://localhost/css/site.css
[HTTP/1.1 404 Not Found 4ms]
	
GET
http://localhost/MUnique.OpenMU.Web.AdminPanel.styles.css
[HTTP/1.1 404 Not Found 0ms]

	
GET
http://localhost/_content/Blazored.Modal/blazored-modal.css
[HTTP/1.1 404 Not Found 0ms]

GET
http://localhost/_content/Blazored.Modal/blazored.modal.js
[HTTP/1.1 404 Not Found 4ms]

[Copilot]

It does not work yet. I started the Startup project and opened the admin panel in the browser. It can't get some static web assets:

GET...

Fixed in commit 74fc606. The issue was that App.razor files were using incorrect paths for static assets. In the new Blazor Web App pattern, the App.razor component doesn't have access to Razor Page helpers like ~ or Url.Content(), so all static assets must use their full _content/ paths.

Changes made:

• Fixed AdminPanel App.razor: css/site.css → _content/MUnique.OpenMU.Web.Shared/css/shared.css (site.css didn't exist)
• Fixed AdminPanel App.razor: MUnique.OpenMU.Web.AdminPanel.styles.css → _content/MUnique.OpenMU.Web.AdminPanel/MUnique.OpenMU.Web.AdminPanel.styles.css
• Removed non-existent _content/MUnique.OpenMU.Web.Map/css/site.css from Map and GameServer.Host App.razor files
• Fixed scoped CSS paths in AdminPanel.Host and GameServer.Host to use _content/ prefix

The static assets should now load correctly.

[sven-n]

The page opens, but it's not functional. We have now the following errors when loading the AdminPanel page:

GET
http://localhost/_content/Blazored.Modal/blazored-modal.css
[HTTP/1.1 404 Not Found 8ms]

GET
http://localhost/_content/Blazored.Modal/blazored.modal.js
[HTTP/1.1 404 Not Found 47ms]

GET
http://localhost/_content/MUnique.OpenMU.Web.AdminPanel/_content/Blazored.Toast/Blazored.Toast.bundle.scp.css
[HTTP/1.1 404 Not Found 2ms]

GET
http://localhost/_content/MUnique.OpenMU.Web.AdminPanel/_content/Blazored.Modal/Blazored.Modal.bundle.scp.css
[HTTP/1.1 404 Not Found 2ms]

GET
http://localhost/_content/MUnique.OpenMU.Web.AdminPanel/_content/MUnique.OpenMU.Web.ItemEditor/MUnique.OpenMU.Web.ItemEditor.jwdwu43srf.bundle.scp.css
[HTTP/1.1 404 Not Found 2ms]

GET
http://localhost/_content/MUnique.OpenMU.Web.AdminPanel/_content/Microsoft.AspNetCore.Components.QuickGrid/Microsoft.AspNetCore.Components.QuickGrid.boiwgh0w5b.bundle.scp.css
[HTTP/1.1 404 Not Found 1ms]

GET
http://localhost/_content/MUnique.OpenMU.Web.AdminPanel/_content/MUnique.OpenMU.Web.Shared/MUnique.OpenMU.Web.Shared.c0g0rwfzu1.bundle.scp.css
[HTTP/1.1 404 Not Found 1ms]

[Copilot]

The page opens, but it's not functional. We have now the following errors when loading the AdminPanel page:

GET...

The issue is caused by a conflict between two requirements:

1. Static Web Assets Bug Workaround: The FixNetSdkDiscoverAssetsBug target in Startup.csproj is necessary to avoid build errors when a web project references another web project (a known .NET SDK issue: The "DiscoverPrecompressedAssets" task failed unexpectedly dotnet/sdk#52089)

2. Static Web Assets Manifest: The Startup project needs a consolidated MUnique.OpenMU.Startup.staticwebassets.runtime.json manifest file to serve static assets from its dependencies (AdminPanel, Blazored packages, etc.)

The workaround prevents the manifest from being generated properly, causing the 404 errors.

Temporary Solution:
Run the AdminPanel.Host or GameServer.Host projects directly instead of Startup. These projects have their own App.razor files and are configured to work correctly:

• src/Dapr/AdminPanel.Host - runs AdminPanel standalone
• src/Dapr/GameServer.Host - runs GameServer with Map app

Permanent Solution (requires further work):
The Startup project needs a different approach - either:

1. Use a custom MSBuild target that generates the manifest after deduplication
2. Create a host-specific App.razor in Startup instead of using AdminPanel's App.razor
3. Wait for the .NET SDK bug to be fixed and remove the workaround

Commits d0256fc attempted to fix paths and middleware order, but the root cause is the missing manifest file.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• http://crl3.digicert.com:443/sha2-assured-ts.crl
  • Triggering command: /usr/bin/dotnet dotnet build src/MUnique.OpenMU.sln --configuration Release (http block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

[sven-n]

@copilot can you review my changes?

[Copilot]

@copilot can you review my changes?

I've reviewed your changes in commit f8c8be5. Here's my assessment:

✅ Good Changes

1. Proper Blazor Web App Structure

• Moved from root App.razor to Components/App.razor - follows .NET 10 conventions
• Created Components/Routes.razor to separate routing logic
• Moved layouts to Components/Layout/ directory structure
• Added ReconnectModal components with proper styling and JS interop

2. Asset Management Improvements

• Using @Assets["..."] helper for static asset paths - solves the 404 issues we discussed
• ResourcePreloader and ImportMap components for better performance
• Properly references MUnique.OpenMU.Startup.styles.css for scoped styles

3. Router Configuration

• NotFoundPage attribute on Router component for proper 404 handling
• Added dedicated NotFound.razor pages

⚠️ Minor Issues

1. Routes.razor (line 1): Missing @ symbol before typeof

<Router AppAssembly="typeof(Program).Assembly"

Should be:

<Router AppAssembly="@typeof(Program).Assembly"

2. WebApplicationExtensions.cs (line 20): Namespace updated to include .Components but verify all references are correct

3. Styling: MainLayout moved from <div class="main"> to <main> element - semantic improvement but verify CSS still works

✅ Summary

Your changes successfully complete the Blazor Web App migration and solve the static asset loading issues. The new structure with @Assets helper and proper component organization follows best practices. Build passes successfully.

Main improvement needed: Fix the missing @ symbol in Routes.razor files.

[sven-n]

Okay, I added the missing @s, even if they're not needed. The don't hurt, it still works.