Blazor WASM app fails to start on ASP.NET Core 10.0.0-preview4 and -preview5

[zotanmew]

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

During regular net10 upgrade testing I discovered that our Blazor WASM application doesn't start successfully when referencing ASP.NET core dependencies of version 10.0.0-preview.4 or 10.0.0-preview.5, it still starts up perfectly normally on 10.0.0-preview.3.

We're depending on the following ASP.NET Core packages:

<PackageReference Include="Microsoft.AspNetCore.Components.Authorization" Version="10.0.0-preview.4.25258.110" />
<PackageReference Include="Microsoft.AspNetCore.Components.WebAssembly" Version="10.0.0-preview.4.25258.110" />
<PackageReference Include="Microsoft.AspNetCore.SignalR.Client" Version="10.0.0-preview.4.25258.110" />
<PackageReference Include="Microsoft.AspNetCore.SignalR.Protocols.MessagePack" Version="10.0.0-preview.4.25258.110" />
<PackageReference Include="Microsoft.Extensions.Localization" Version="10.0.0-preview.4.25258.110" />
<PackageReference Include="Microsoft.Extensions.Logging.Configuration" Version="10.0.0-preview.4.25258.110" />

The error message encountered:

[MONO] /__w/1/s/src/runtime/src/mono/mono/metadata/custom-attrs.c:1987 <disabled>

Error: One or more errors occurred. (Could not resolve type with token 010000e9 from typeref (expected class 'Microsoft.Extensions.Logging.ProviderAliasAttribute' in assembly 'Microsoft.Extensions.Logging.Abstractions, Version=10.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60'))

.NET Version

10.0.100-preview.4.25258.110

[MattParkerDev]

Have you deleted the bin and obj folders and rebuilt, and opened the app in a new incognito window?

[dotnet-policy-service]

Thank you for filing this issue. In order for us to investigate this issue, please provide a minimal repro project that illustrates the problem without unnecessary code. Please share with us in a public GitHub repo because we cannot open ZIP attachments, and don't include any confidential content.

[zotanmew]

Have you deleted the bin and obj folders and rebuilt, and opened the app in a new incognito window?

A clean rebuild does indeed solve the issue, apologies for not trying that before opening an issue. Thank you!