Blazor WebAssembly AOT failed with VS2022 17.12.1 Professional #110038
Labels
arch-wasm
WebAssembly architecture
area-Codegen-AOT-mono
needs-author-action
An issue or pull request that requires more info or actions from the author.
os-browser
Browser variant of arch-wasm
Milestone
Description
Blazor WebAssembly AOT failed with VS2022 17.12.1 Professional.
Reproduction Steps
Expected behavior
Blazor WebAssembly AOT compiling is done sucessfully without error messages and all files are created in publish folder.
Actual behavior
The AOT compiling produces the following output and the publish failed:
AOTTest failed with 15 error(s) (1,0s) C:\Program Files\dotnet\packs\Microsoft.NET.Runtime.WebAssembly.Sdk\9.0.0\Sdk\WasmApp.Common.targets(694,5): error : Precompiling failed for C:\Users\Gensoft-Yazılım\source\repos\AOTTest\AOTTest\obj\release\net9.0\wasm\for-publish\aot-in\Microsoft.Exten sions.Configuration.Json.dll with exit code 1. The specified response file can not be read C:\Program Files\dotnet\packs\Microsoft.NET.Runtime.WebAssembly.Sdk\9.0.0\Sdk\WasmApp.Common.targets(694,5): error : Precompiling failed for C:\Users\Gensoft-Yazılım\source\repos\AOTTest\AOTTest\obj\release\net9.0\wasm\for-publish\aot-in\Microsoft.Exten sions.Logging.dll with exit code 1. The specified response file can not be read C:\Program Files\dotnet\packs\Microsoft.NET.Runtime.WebAssembly.Sdk\9.0.0\Sdk\WasmApp.Common.targets(694,5): error : ons.Concurrent.dll with exit code 1.xit code 1. exit code 1.s\AOTTest\AOTTest\obj\release\net9.0\wasm\for-publish\aot-in\Microsoft.Exten The specified response file can not be read AOTTest failed (2,2s) → bin\release\net9.0\wwwroot Precompiling failed for C:\Users\Gensoft-Yazılım\source\repos\AOTTest\AOTTest\obj\release\net9.0\wasm\for-publish\aot-in\System.Collecti Build failed with 15 error(s) in 4,2s
Regression?
Bu senaryo, .Net 8 de denendi. ancak aynı hata ile karşılaşıldı.
Known Workarounds
Currently I do not know about workarounds of this issue.
Configuration
Other information
No response
The text was updated successfully, but these errors were encountered: