avalonia.js 404

[githubxiaoa]

Describe the bug

avalonia.js 404

To Reproduce

not run

Expected behavior

No response

Avalonia version

11.1.0

OS

Windows, WebAssembly

Additional context

No response

[maxkatz6]

Try to recreate browser project from the avalonia.xplat template.

[githubxiaoa]

I have created a new project without making any changes, but it is still unsuccessful

[msneijders]

Using template v1.14 it works running from visual studio (it finds and reads an avalonia.js file) -- but when I deploy (testing with a local IIS), I cannot find the avalonia.js file in _framework folder. I copied the content from avalonia.js that is generated while debugging from visual studio from within the browsers DevTools (because I cannot find it in wwwroot/_framework), and put it in the _framework folder of the deployment; then it runs.

[maxkatz6]

I have created a new project without making any changes, but it is still unsuccessful

It doesn't give much information on how you run it.
New project templates work just fine here, via dotnet run and dotnet publish (which are the most important).
If any IDE doesn't handle running projects - report the issue to them.

testing with a local IIS

Can't really help with IIS. Don't see reasons to use it also.
For local testing of published packages, I recommend dotnet serve tool. For production there are various static website cloud providers as well, or nginx should work too just fine.

but when I deploy

Do you deploy with dotnet publish btw? Any other way won't work.

[msneijders]

Do you deploy with dotnet publish btw? Any other way won't work.

😳 I used 'publish' from within visual studio -- naively thinking that should work, it does keep saying 'publish succeeded'. But simply using dotnet publish I do get a full subfolder '_framework', containing the avalonia.js.

[ztl8702]

I noticed that the avalonia.js StaticWebAsset item is created with SourceType=Package:

Avalonia/src/Browser/Avalonia.Browser/build/Microsoft.AspNetCore.StaticWebAssets.props

Line 9 in 0bd90d8

<SourceType>Package</SourceType>

However, when I inspect the MSBuild binlog for a project that consumes Avalonia.Browser transitively, I noticed that dotnet.js ends up having SourceType=Computed. (I don't know how/why, since StaticWebAssetSdk is not well documented. But the key here is that avalonia.js has different metadata than dotnet.js):

And hence it is skipped by the CopyStaticWebAssetsToOutputDirectory target. (SDK source)

I am using .NET SDK 9.0.100-preview.3.24204.13. The project targets .NET 8.0.

MSBuild Binlog of the consuming project:
build.binlog.zip

[ztl8702]

Note that for me dotnet publish does output avalonia.js correctly. I am specifically talking about the following use-case:

• (1) Main Project (AspNetCore web server app)
  • references a (2) Microsoft.NET.Sdk.WebAssembly project (with ReferenceOutputAssembly="false" SkipGetTargetFrameworkProperties="true" OutputItemType="Content", to consume its static content),
    • which references Avalonia.Browser

directly publishing (2) will work. But building (1) does not correctly copy avalonia.js to (1), whereas dotnet.js will be copied to (1).

Adding Avalonia.Browser directly to (1) does not fix the issue either.

[ITDancer13]

I had the same issue. Running dotnet workload install wasm-tools and rebuilding everything fixed it. The default application of the template works.

[suprak]

I had the same issue. Running dotnet workload install wasm-tools and rebuilding everything fixed it. The default application of the template works.

After installing wasm tools and even restarting VS, launching from VS did not work for me.
Running dotnet run from the Browser project folder did work.