Compiled WASM output differs on my development machine

[sdijoseph]

When trying to build and run my Blazor WASM project on my PC, when I try to load a particular component using SkiaSharp, I get this exception:

Microsoft.AspNetCore.Components.WebAssembly.Rendering.WebAssemblyRenderer[100]
      Unhandled exception rendering component: ReferenceError: GL is not defined
Microsoft.JSInterop.JSException: ReferenceError: GL is not defined
 ---> ReferenceError: GL is not defined
   Exception_EndOfInnerExceptionStack
   at Microsoft.JSInterop.WebAssembly.WebAssemblyJSRuntime.InvokeJS(String , String , JSCallResultType , Int64 )
   at Microsoft.JSInterop.JSInProcessRuntime.Invoke[GLInfo](String , Int64 , Object[] )
   at Microsoft.JSInterop.Implementation.JSInProcessObjectReference.Invoke[GLInfo](String , Object[] )
   at SkiaSharp.Views.Blazor.Internal.JSModuleInterop.Invoke[GLInfo](String identifier, Object[] args)
   at SkiaSharp.Views.Blazor.Internal.SKHtmlCanvasInterop.InitGL()
   at SkiaSharp.Views.Blazor.SKGLView.OnAfterRenderAsync(Boolean firstRender)
   at Microsoft.AspNetCore.Components.RenderTree.Renderer.GetErrorHandledTask(Task , ComponentState )

However, when I re-built the project on a remote build server, downloaded the published artifact, and ran that from my PC, the component loaded correctly. I analyzed the difference in the publish output from the build server and my PC, and I narrowed the issue down to the Blazor framework files (in wwwroot/_framework). When I replaced the contents of this folder from the working version to the failing version, the issue disappeared.

I ran a diff on the _framework folder to see which files where different, and got this output:

Files WorkingProject\_framework/HarfBuzzSharp.wasm and FailingProject\_framework/HarfBuzzSharp.wasm differ
Files WorkingProject\_framework/HarfBuzzSharp.wasm.br and FailingProject\_framework/HarfBuzzSharp.wasm.br differ
Files WorkingProject\_framework/HarfBuzzSharp.wasm.gz and FailingProject\_framework/HarfBuzzSharp.wasm.gz differ
Files WorkingProject\_framework/SkiaSharp.wasm and FailingProject\_framework/SkiaSharp.wasm differ
Files WorkingProject\_framework/SkiaSharp.wasm.br and FailingProject\_framework/SkiaSharp.wasm.br differ
Files WorkingProject\_framework/SkiaSharp.wasm.gz and FailingProject\_framework/SkiaSharp.wasm.gz differ
Files WorkingProject\_framework/MyProject.Api.Client.pdb.gz and FailingProject\_framework/MyProject.Api.Client.pdb.gz differ
Files WorkingProject\_framework/MyProject.Api.Client.wasm and FailingProject\_framework/MyProject.Api.Client.wasm differ
Files WorkingProject\_framework/MyProject.Api.Client.wasm.br and FailingProject\_framework/MyProject.Api.Client.wasm.br differ
Files WorkingProject\_framework/MyProject.Api.Client.wasm.gz and FailingProject\_framework/MyProject.Api.Client.wasm.gz differ
Files WorkingProject\_framework/MyProject.Client.pdb.gz and FailingProject\_framework/MyProject.Client.pdb.gz differ
Files WorkingProject\_framework/MyProject.Client.wasm and FailingProject\_framework/MyProject.Client.wasm differ
Files WorkingProject\_framework/MyProject.Client.wasm.br and FailingProject\_framework/MyProject.Client.wasm.br differ
Files WorkingProject\_framework/MyProject.Client.wasm.gz and FailingProject\_framework/MyProject.Client.wasm.gz differ
Files WorkingProject\_framework/MyProject.Shared.pdb.gz and FailingProject\_framework/MyProject.Shared.pdb.gz differ
Files WorkingProject\_framework/MyProject.Shared.wasm and FailingProject\_framework/MyProject.Shared.wasm differ
Files WorkingProject\_framework/MyProject.Shared.wasm.br and FailingProject\_framework/MyProject.Shared.wasm.br differ
Files WorkingProject\_framework/MyProject.Shared.wasm.gz and FailingProject\_framework/MyProject.Shared.wasm.gz differ
Files WorkingProject\_framework/blazor.boot.json and FailingProject\_framework/blazor.boot.json differ
Files WorkingProject\_framework/blazor.boot.json.br and FailingProject\_framework/blazor.boot.json.br differ
Files WorkingProject\_framework/blazor.boot.json.gz and FailingProject\_framework/blazor.boot.json.gz differ
Only in WorkingProject\_framework: dotnet.native.8.0.4.9npnv5bs00.js
Only in WorkingProject\_framework: dotnet.native.8.0.4.9npnv5bs00.js.br
Only in WorkingProject\_framework: dotnet.native.8.0.4.9npnv5bs00.js.gz
Only in FailingProject\_framework: dotnet.native.8.0.4.rkw194kvb3.js
Only in FailingProject\_framework: dotnet.native.8.0.4.rkw194kvb3.js.br
Only in FailingProject\_framework: dotnet.native.8.0.4.rkw194kvb3.js.gz
Files WorkingProject\_framework/dotnet.native.wasm and FailingProject\_framework/dotnet.native.wasm differ
Files WorkingProject\_framework/dotnet.native.wasm.br and FailingProject\_framework/dotnet.native.wasm.br differ
Files WorkingProject\_framework/dotnet.native.wasm.gz and FailingProject\_framework/dotnet.native.wasm.gz differ

I tried completely uninstalling the .NET 8 SDK and all workloads, then re-installing both the SDK and the wasm-tools workload. I still see the same differences in .wasm file output.

Does anyone know what could be the difference on my machine vs others causing the differing publish output?

[sdijoseph]

I believe I fixed this issue. I tried building my project in a VM and I noticed that I got different output when I tried running workload restore.

VM:

$ dotnet workload restore
Installing workloads:


Successfully installed workload(s) wasm-tools.

Problem machine:

dotnet workload restore
__________________________________________________
Project "C:\Users\user\RiderProjects\MyProjectsite\MyProject.Client\MyProject.Client.csproj" (_GetRequiredWorkloads target(s)):

C:\Users\user\RiderProjects\MyProjectsite\MyProject.Client\MyProject.Client.csproj : error MSB4057: The target "_GetRequiredWorkloads" does not exist in the project.
Done building project "MyProject.Client.csproj" -- FAILED.
Failed to restore workload for project C:\Users\user\RiderProjects\MyProjectsite\MyProject.Client\MyProject.Client.csproj: Failed to run MSBuild Target _GetRequiredWorkloads.

I tried completely uninstalling and reinstalling the .NET 8 SDK, and that still didn't fix the problem. It turned out that I had an environment variable "MSBuildEnableWorkloadResolver" set to false for some reason. Removing that variable, completely cleaning the project, running workload restore again, and then rebuilding fixed my issue.