fix: CtorNotLocated exception while using progress toasts with Blazor WASM

[MysteryMS]

🐛 Bug Report

This is a reopening of #3408 since it had no recent activities since I last commented and this issue still persists.

When compiling Web Assembly, showing a progress toast gives an unhandled exception on production builds, but not on development.

💻 Repro or Code Sample

        ToastParameters<ProgressToastContent> progressToast = new()
        {
            Intent = ToastIntent.Progress,
            Timeout = 0,
            Title = "Generating PDF",
            Content = new()
            {
                Details = "This may take a few seconds"
            }
        };
        ToastService.ShowProgressToast(progressToast);

🤔 Expected Behavior

Toast should show with no exceptions

😯 Current Behavior

Unhandled exception is thrown:
Microsoft.AspNetCore.Components.WebAssembly.Rendering.WebAssemblyRenderer[100] Unhandled exception rendering component: CtorNotLocated, Microsoft.FluentUI.AspNetCore.Components.ProgressToast

💁 Possible Solution

As stated on #3408

<PropertyGroup>
  <BlazorWebAssemblyEnableLinking>false</BlazorWebAssemblyEnableLinking>
</PropertyGroup>

However, that did not seem to take effect.

Tried also configuring the Linker with a config file:

<?xml version="1.0" encoding="UTF-8" ?>
<linker>
    <assembly fullname="Microsoft.FluentUI.AspNetCore.Components.ProgressToast">
    </assembly>
</linker>

No luck.

🔦 Context

🌍 Your Environment

• OS & Device: Linux on PC, Ubuntu 24.04
• Browser: Microsoft Edge, Chrome
• .NET and Fluent UI Blazor library Version: .NET 9.0.102 and Fluent UI 4.12.0

[vnbaaij]

Supply as many details as you can on how you are running production builds.

As you saw in the other issue, it usually runs fine locally even with a release build. For us it runs fine on the live demo environment (wich is WASM) as well.

We need more details if you want us to help and look into it. We simply do not have capacity to go on a quest ourselves.

[MysteryMS]

Prod builds are run through Netlify, built through dotnet publish, the Netlify CLI takes care of uploading the content at /bin/Release/net9.0/publish/wwwroot

Before Netlify, I used to upload it myself to a server and serve it through reverse proxy with Nginx, and I used to have the same problem with the toasts

[vnbaaij]

But what is it running on? I can't help if I can't reproduce your issue...

[MysteryMS]

Sorry for the misunderstanding - you mean the environment? It runs on Ubuntu 24.04

[DanielCordell]

I've had this issue before as well actually, but on Windows 10 10.0.20348, dotnet 8.0.411.

Local builds work fine, publish builds break with this error. I assume the inner utility components are being trimmed out somehow?

[vnbaaij]

Please verify if your issue is resolved in your environment by testing with our preview packages