Avalonia Browser does not work with 11.2.3

[luoczeng]

Hi, I've got an Avalonia project, desktop/android/ios all work fine except for the browser. There is nothing showing up except the Avalonia trademark. The official Avalonia browser sample does not work for me neither.
I have updated the dotnet workload and have upgraded all .NET SDK versions to latest, still no luck.
Can anyone help on that? Thanks!

Official ControlCatalog.Browser does not work for me after updating the workload.

I have upgraded all .net SDK versions to latest:

All dotnet workload have been upgraded to latest as of now.

[timunie]

You need the workload to match your NET version. So if your project is Net8, workload needs to be also in version 8

[luoczeng]

Hi,
I just uninstall .NET 9.0 SDK and uninstalled 'wasm-tools' workload, then use 'dotnet workload install wasm-tools' to reinstall it.

However ControlCatalog.Browser still shows a blank avalonia trademark for me.

Can you suggest where I could possibly be doing wrong? Thanks!

[timunie]

Doesn't it use Net8? Or did you change the proj?

Anyways, sometimes it also helps to clean browser cache.

[luoczeng]

Okay, finally I figured it out myself.
After dotnet publish and dotnet serve to host the wasm locally, magically the avalonia.js is missing in the _framework folder. We can see the 404 error in the console window or developer tools.

After searching for avalonia.js on my PC, I happen to find one in a totally different project output folder, which I have no idea how it gets created. After manually copy this file to my 'bin\Release\net8.0-browser\publish\wwwroot_framework' folder, the application can run now.

[maxkatz6]

DO NOT manually copy this file. It's a hack, not a solution.
This error typically happens with problems with .NET SDK and WASM workloads setup, and doesn't happen under normal conditions.

[wizardness]

How hard would it be to add a build-time error if avalonia.js is not created?