You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Blazor WebAssembly AOT failed with VS2022 17.12.1 Professional.
Reproduction Steps
Create a new Blazor WebAssembly Standalone App
Set true in the project file.
Try to publish the project with the following command: dotnet publish -c Release
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
.NET version: 9.0.100
OS: Windows 10 Pro 22H2
Processor: Intel(R) Core(TM) i5-10400 CPU @ 2.90GHz 2.90 GHz
Visual Studio: Microsoft Visual Studio Professional 2022 (64-bit) - Current Version 17.12.1
Other information
No response
The text was updated successfully, but these errors were encountered:
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: