Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

fix: blazor wasm AOT in net7 rc2

See original GitHub issue

🐛 Bug Report

Opening a new issue to provide visibility to this since I didn’t get a reply to #214 but it’s essentially the same thing.

💻 Repro or Code Sample

<RunAOTCompilation>true</RunAOTCompilation>
<RunAOTCompilationAfterBuild>true</RunAOTCompilationAfterBuild>
<WasmNativeStrip>false</WasmNativeStrip>

project targeting net7

dotnet publish -c Release

🤔 Expected Behavior

AOT and assembly trimming to function properly.

😯 Current Behavior

getting the following error message

C:\Program Files\dotnet\packs\Microsoft.NET.Runtime.WebAssembly.Sdk\7.0.0-rc.2.22472.3\Sdk\WasmApp.Native.targets(583,5): error : Precompiling failed for <...>\obj\release\net7.0\linked\Microsoft.Fast.Components.FluentUI.dll with exit code -1073741571.

💁 Possible Solution

🔦 Context

🌍 Your Environment

OS & Device: [e.g. MacOS, iOS, Windows, Linux] on [iPhone 7, PC] windows 11 x64
Browser [e.g. Microsoft Edge, Google Chrome, Apple Safari, Mozilla FireFox] N/A
.NET and FAST Version [e.g. 1.8.0] 7.0.0-rc.2.22472.3, 1.6.0-rc.2 CC @MertUssakliMSFT

Issue Analytics

State:
Created a year ago
Reactions:1
Comments:5 (1 by maintainers)

Top GitHub Comments

1reaction

vnbaaijcommented, Nov 3, 2022

The plan was to get it out in the final 1.6 release (together with the .NET 7 release). But I can also do a 1.6.0-rc.3 release after @MertUssakliMSFT has done some tests.

0reactions

MertUssakliMSFTcommented, Nov 14, 2022

Sorry about the delay, I can confirm that the fix works.