Marek Fišera

What version of System.Text.Json does the .NET framework MSBuild include? Are the tests using new enough VS?

It happens during publish on ILLinked dlls. The `System.Private.Xml.dll` could have been linked to "0", but there is no chance it could happen for `System.Private.CoreLib.dll`. It looks like some race...

Also https://github.com/dotnet/runtime/issues/101154 in which is was caused by publish run in parallel. @SilverioMiranda Are you publishing only a server project or whole solution?

A possible workaround could be to generate temp webcil files to a guid-containing folder

We have landed an improvement that was planned for 10. Moving to backlog for known build error tracking

@SilverioMiranda Thank you! There will be a change in RC2 that minimizes the possibility for collision. As a workaround you can do publish for Web App Server + the API...

I tested it today with `8.0.100-preview.4.23220.2` - `/p:WasmEnableThreads=true` is passed to the "run" process (as documentation says) - both `-p:WasmEnableThreads=true` and `--property:WasmEnableThreads=true` are ignored I have a simple console project...

The links from https://github.com/dotnet/runtime/issues/90458#issuecomment-2980936495 doesn't work for me :/ The latest error in the table is `failed (returned 137)` ``` [] /root/helix/work/workitem/e/dotnet-latest/packs/Microsoft.NET.Runtime.WebAssembly.Sdk/8.0.20/Sdk/WasmApp.Native.targets(388,5): error : emcc: error: '/root/helix/work/workitem/e/dotnet-latest/packs/Microsoft.NET.Runtime.Emscripten.3.1.34.Sdk.linux-x64/8.0.20/tools/bin/clang++ -target wasm32-unknown-emscripten -fvisibility=default...

> As a result of discussion in https://github.com/dotnet/aspnetcore/issues/64282#issuecomment-3532754642 I believe that the steps of publishing a standalone wasm app need to have the clarification that you have to disable fingerprinting...

Is it a duplicate of https://github.com/dotnet/xharness/issues/974?