[WASM] AOT build fails. unoapp-winui-net6 template

[emceelovin]

I've tried everything in issue #7740, but I can't seem to get the AOT release to build. The supplied screenshot of the build log is as far as can dig into the error. I've troubleshooted and built the project with all of the steps in Troubleshooting build issues. I followed all of the steps in the AOT Build .NET AOT for WebAssembly in Visual Studio with Uno Platform. However, while I did all of those steps, a window did not popup asking me to run a script, but I manually ran everything in the supplied script in the article. Except, I got some errors. I had to install dotnet-3.1. dotnet-3.0 wouldn't install. It required some kind of library dependency. When I build my wasm project in release and AOT enabled, the build partially succeeds. The console pops up, and then I get this build error:

I have everything set to diagnostics level output, but I cant seem to get more information out of this error. I've built with the most verbose settings and all of the commands listed in the troubleshooting. Still can't get this to build.

msbuid.binlog.zip

EDIT
Apparently, Uno.Wasm.Bootstrap.Cli got uninstalled somehow, but once I installed it, I get these errors in addition to the other errors no
binlog.zip
w

This is the latest error I get with these as my project dependencies. If I uncommenting the MVC dependencies don't fix anything:

[jeromelaban]

Thanks for the report. You seem to be having an extra option that's not needed anymore <ExtraEmccFlags Include="-lidbfs.js" />.

Can you try removing it and see if it helps ?

[emceelovin]

No problem! Really appreciate all that's being done, and I like to help anytime I can when I find an issue.

[emceelovin]

Well now that I am able to build Uno projects again on the latest 17.1, I still am not able to get wasm AOT working. This is the error i get, and the package references my project has:

<Project Sdk="Microsoft.NET.Sdk.Web">
  <PropertyGroup>
    <OutputType>Exe</OutputType>
    <TargetFramework>net6.0</TargetFramework>
    <NoWarn>NU1701</NoWarn>
	  <WasmShellMonoRuntimeExecutionMode Condition="'$(Configuration)'=='Release'">InterpreterAndAOT</WasmShellMonoRuntimeExecutionMode>
  </PropertyGroup>
	<PropertyGroup Condition="'$(Configuration)'=='Debug'">
    <MonoRuntimeDebuggerEnabled>true</MonoRuntimeDebuggerEnabled>
    <DefineConstants>$(DefineConstants);TRACE;DEBUG</DefineConstants>
    <DebugType>portable</DebugType>
    <DebugSymbols>true</DebugSymbols>
    <!--
		IL Linking is disabled in Debug configuration.
		When building in Release, see https://platform.uno/docs/articles/features/using-il-linker-webassembly.html
		-->
    <WasmShellILLinkerEnabled>false</WasmShellILLinkerEnabled>
  </PropertyGroup>
  <ItemGroup>
    <Content Include="Assets\SplashScreen.png" />
  </ItemGroup>
  <ItemGroup>
    <UpToDateCheckInput Include="..\OneGreatTeam.Shared\**\*.xaml" />
  </ItemGroup>
  <ItemGroup>
    <EmbeddedResource Include="WasmCSS\Fonts.css" />
    <EmbeddedResource Include="WasmScripts\AppManifest.js" />
  </ItemGroup>
  <ItemGroup>
    <LinkerDescriptor Include="LinkerConfig.xml" />
  </ItemGroup>
  <ItemGroup>
    <!--
		This item group is required by the project template because of the
		new SDK-Style project, otherwise some files are not added automatically.

		You can safely remove this ItemGroup completely.
		-->
    <None Include="Program.cs" />
    <None Include="LinkerConfig.xml" />
    <None Include="wwwroot\web.config" />
</ItemGroup>
<ItemGroup>
    <PackageReference Include="Microsoft.Windows.Compatibility" Version="5.0.0" />
    <PackageReference Include="Microsoft.Extensions.Logging" Version="5.0.0" />
    <PackageReference Include="System.Reflection.Emit.Lightweight" Version="4.7.0" />
    <PackageReference Include="System.Threading.Channels" Version="6.0.2-mauipre.1.22054.8" />
    <PackageReference Include="Uno.Extensions.Logging.WebAssembly.Console" Version="1.0.1" />
    <PackageReference Include="Uno.WinUI.WebAssembly" Version="4.1.0-dev.545" />
    <PackageReference Include="Uno.WinUI.RemoteControl" Version="4.0.11" Condition="'$(Configuration)'=='Debug'" />
    <PackageReference Include="Uno.UI.Adapter.Microsoft.Extensions.Logging" Version="4.0.11" />
    <PackageReference Include="Uno.Wasm.Bootstrap" Version="3.2.0-dev.24" />
    <PackageReference Include="Uno.Wasm.Bootstrap.DevServer" Version="3.2.0-dev.24" />
    <PackageReference Include="Uno.Wasm.Bootstrap.Cli" Version="1.1.0-dev.445" />
</ItemGroup>
<Import Project="..\OneGreatTeam.Shared\OneGreatTeam.Shared.projitems" Label="Shared" Condition="Exists('..\OneGreatTeam.Shared\OneGreatTeam.Shared.projitems')" />
</Project>

even if i add the Microsoft.AspnetCore.Mvc.Core project to my package references, I still can't get it to build. If i remove the Uno.Wasm.Bootstrap.Cli package reference, the build process just sits at loading the .wasm.dll. When I look at task manager, a bunch of clang+++ and python.exe's are doing something though. They come and then disappear. Come and disappear. If i drop the Uno.Wasm.Bootstrap.Cli package to 1.1.0-dev.416, I no longer get the MVC error, but it still just sits at "1>OneGreatTeam.Wasm -> C:\Users\jeffc\source\repos\One Great Team\uno\OneGreatTeam\OneGreatTeam.Wasm\bin\Release\net6.0\OneGreatTeam.Wasm.dll"

[jeromelaban]

Thanks for the update. The Uno.Wasm.Bootstrap.Cli package is deprecated and is not needed anymore.

When troubleshooting issues, make sure to start from the official templates to check if a vanilla configuration works, either by creating a new project from visual studio, or by using dotnet new templates.

[emceelovin]

Oh ok. I didn't know it was deprecated. There are quite a few wasm AOT docs, but I think i did notice that the github wasm AOT doc didn't reference that package. I can't remember if i created this project via dotnet or VS. I'm pretty sure I created it via dotnet new uno-app-winui-net6. I will try creating a new project and see if it works, and if it does, I will just move everything over, but I figured I would give any info I could to help things along. Thank you for the help once again. It probably is an older template.

[emceelovin]

I just created a new unoapp-winui-net6 template, which had a template update even though i checked the template version the other day and was on the latest, and the AOT wasm built, so thank you!

EDIT: Apparently, Interpreter likes to work, but InterpreterAndAOT just sits at loading the .wasm.dll and pinning my CPU at 100%. I guess its trying to compile something, but a test project is tiny. It shouldn't take this long?

I'm back to WindowsAppSDK version errors again, and I forgot how i cleared those up last time. Gonna try and get this together....