We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgraded the project to .net6, everything works fine. But Enabling the AOT makes publish command fails
Attached the msbuild log file for reference. msbuild.zip .
Publish the Application using dotnet publish -c Release. AOT precompiling fails.
dotnet publish -c Release
Publish the wasm project with AOT.
precompilation fails while aoting the Syncfusion.Blazor.Diagram.dll
Syncfusion.Blazor.Diagram.dll
No response
The text was updated successfully, but these errors were encountered:
Tagging subscribers to 'arch-wasm': @lewing See info in area-owners.md if you want to be subscribed.
arch-wasm, untriaged, area-Codegen-AOT-mono
arch-wasm
untriaged
area-Codegen-AOT-mono
Sorry, something went wrong.
Closing as a dupe of #61053 .
It fails because mono-aot-cross runs out of stack space, and was fixed on main but didn't make it into 6.0. You can either try the 7.0*alpha build from https://github.com/dotnet/installer/#installers-and-binaries or wait for 6.0.1 release.
mono-aot-cross
main
6.0
Also, see #61053 (comment) for a possible workaround.
No branches or pull requests
Description
Upgraded the project to .net6, everything works fine. But Enabling the AOT makes publish command fails
Attached the msbuild log file for reference.
msbuild.zip
.
Reproduction Steps
Publish the Application using
dotnet publish -c Release
. AOT precompiling fails.Expected behavior
Publish the wasm project with AOT.
Actual behavior
precompilation fails while aoting the
Syncfusion.Blazor.Diagram.dll
Regression?
No response
Known Workarounds
No response
Configuration
Other information
No response
The text was updated successfully, but these errors were encountered: