When a web app references an Sdk.WebAssembly project, the error "The UpdateExternallyDefinedStaticWebAssets task failed unexpectedly" appears during compilation

[dczuo]

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

The "UpdateExternallyDefinedStaticWebAssets" task failed unexpectedly.
System.InvalidOperationException: No file exists for the asset at either ___location 'C:\Users\dczuo\source\repos\WebApplication1\WebAssembly1\bin\Debug\net9.0\wwwroot_framework\WebAssembly1.pdb' or 'obj\Debug\net9.0\WebAssembly1.pdb'.
at Microsoft.AspNetCore.StaticWebAssets.Tasks.StaticWebAsset.ResolveFile(String identity, String originalItemSpec)
at Microsoft.AspNetCore.StaticWebAssets.Tasks.StaticWebAsset.ApplyDefaults()
at Microsoft.AspNetCore.StaticWebAssets.Tasks.StaticWebAsset.FromV1TaskItem(ITaskItem item)
at System.Linq.Enumerable.WhereSelectArrayIterator2.MoveNext() at System.Linq.Buffer1..ctor(IEnumerable1 source) at System.Linq.Enumerable.ToArray[TSource](IEnumerable1 source)
at Microsoft.AspNetCore.StaticWebAssets.Tasks.UpdateExternallyDefinedStaticWebAssets.Execute()
at Microsoft.Build.BackEnd.TaskExecutionHost.Execute()
at Microsoft.Build.BackEnd.TaskBuilder.d__26.MoveNext()

Expected Behavior

Build success

Steps To Reproduce

1 Create project ASP.NET Core Empty "WebApplication1", framework
2 Add New project Console App "WebAssembly1", framework: .NET 9.0
3 Change the project "WebAssembly1" sdk to "Microsoft.NET.Sdk.WebAssembly"
4 Reference project "WebAssembly1" in project "WebApplication1"
5 Build project "WebApplication1"

Exceptions (if any)

The "UpdateExternallyDefinedStaticWebAssets" task failed unexpectedly.
System.InvalidOperationException: No file exists for the asset at either ___location 'C:\Users\dczuo\source\repos\WebApplication1\WebAssembly1\bin\Debug\net9.0\wwwroot_framework\WebAssembly1.pdb' or 'obj\Debug\net9.0\WebAssembly1.pdb'.
at Microsoft.AspNetCore.StaticWebAssets.Tasks.StaticWebAsset.ResolveFile(String identity, String originalItemSpec)
at Microsoft.AspNetCore.StaticWebAssets.Tasks.StaticWebAsset.ApplyDefaults()
at Microsoft.AspNetCore.StaticWebAssets.Tasks.StaticWebAsset.FromV1TaskItem(ITaskItem item)
at System.Linq.Enumerable.WhereSelectArrayIterator2.MoveNext() at System.Linq.Buffer1..ctor(IEnumerable1 source) at System.Linq.Enumerable.ToArray[TSource](IEnumerable1 source)
at Microsoft.AspNetCore.StaticWebAssets.Tasks.UpdateExternallyDefinedStaticWebAssets.Execute()
at Microsoft.Build.BackEnd.TaskExecutionHost.Execute()
at Microsoft.Build.BackEnd.TaskBuilder.d__26.MoveNext()

.NET Version

9.0.302 regression in 9.0.4

Anything else?

WebApplication1.zip

[ilonatommy]

@dczuo, thank you for your report. It looks like you are trying to manually build the project structure we provide out-of-the-box in our templates. You can do it by running:
dotnet new blazor --interactivity WebAssembly

If you are using Visual Studio, the template should be also available there. Let us know if that worked.

[dczuo]

@dczuo, thank you for your report. It looks like you are trying to manually build the project structure we provide out-of-the-box in our templates. You can do it by running: dotnet new blazor --interactivity WebAssembly

If you are using Visual Studio, the template should be also available there. Let us know if that worked.

Yes, blazor is fine.
Refer to BlazorWasmSdk, put '<StaticWebAssetMakeReferencedAssetOriginalItemSpecAbsolute>true</StaticWebAssetMakeReferencedAssetOriginalItemSpecAbsolute>' into to project WebAssembly1, and it will compile successfully.

[ilonatommy]

Refer to BlazorWasmSdk, put '<StaticWebAssetMakeReferencedAssetOriginalItemSpecAbsolute>true</StaticWebAssetMakeReferencedAssetOriginalItemSpecAbsolute>' into to project WebAssembly1, and it will compile successfully.

@dczuo I am not sure if I understood correctly. Do you mean that you found the fix? Generally, if you want an ASP.NET Core with WebAssembly, it's better to create the desired projects from beginning, not to create other type and rename it manually. You might have missed some important bits when doing that, e.g. look at the project structure alone (I added WasmApp to your solution - you did not have any wwwroot dir before etc):

Command for wasm project template (non-blazor) is dotnet new wasmbrowser. It's available if you have the wasm-tools workload installed: dotnet workload install wasm-tools and template should be installed with dotnet new install Microsoft.NET.Runtime.WebAssembly.Templates.

[ilonatommy]

@maraf, I can reproduce this problem even when creating the projects properly. Why would we need to set StaticWebAssetMakeReferencedAssetOriginalItemSpecAbsolute manually? Should we edit https://github.com/dotnet/sdk/blob/7d093038ebba148c3d03c5b223127e490df4b0d5/src/WasmSdk/Sdk/Sdk.props adding same logic for this property as Blazor targets have?

edit: reproduced also on net10p7.

[javiercn]

@ilonatommy yes, we should.