Blazor server doesn't render pages properly with custom WebApplicationOptions

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

If I use the following code snippet in Program.cs:

    var builder = WebApplication.CreateBuilder(new WebApplicationOptions
    {
        ApplicationName = typeof(Program).Assembly.FullName,
        ContentRootPath = Path.GetFullPath(Directory.GetCurrentDirectory()),
        WebRootPath = "wwwroot",
        Args = args
    });

Blazor server doesn’t show the web page properly.

Expected Behavior

Blazor server renders the pages properly with custom WebApplicationOptions.

Steps To Reproduce

No response

Exceptions (if any)

No response

.NET Version

6.0.9, 6.0.109

Anything else?

No response

[javiercn]

@khteh It’s not obvious to us what is going on here (hence why we marked the issue as investigate).

We will schedule the issue to be looked at in a future milestone based on our triage (To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.) and will provide an update at that point.

A repro project would help to make sure that we can reproduce your exact issue and determine if there is a bug in the framework or a configuration error in the application.

[MackinnonBuck]

@khteh Glad your issue was resolved!

How does that affect the application’s CSS?

By default, ApplicationName is used to resolve the static web assets manifest file, i.e. <ApplicationName>.staticwebassets.runtime.json. So, using typeof(Program).Assembly.FullName effectively causes the manifest file name to be resolved to something like <assembly name>, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null.staticwebassets.runtime.json, which is incorrect. This will cause all requests to static web assets to 404, including CSS files.

Closing this as by-design.