[.NET 9 + WASM + AOT] RELEASE no longer builds

[DierkDroth]

Current behavior

So far I was building the RELEASE version of my solution using the 'use AOT as much as possible' mode <WasmShellMonoRuntimeExecutionMode>InterpreterAndAOT</WasmShellMonoRuntimeExecutionMode>

This no longer works but throws an error (screenshot below).
Also: there are tons of warnings thrown additionally. How would I address these warnings?

You can reproduce by running Minimal.Wasm/Make.bat using this repo:
Minimal.zip

How could I create a RELEASE build with 'as much AOT as possible' and without warnings?

[jeromelaban]

Thanks for the report. Make sure to follow the directions from our release notes.

[DierkDroth]

Trimming warnings in your code generally need to be fixed

That's what I though @jeromelaban. However, as per LinkerConfig.xml snippet above I thought the linker would just leave my 3 assemblies Unusual.Common, Unusual.Gui.Wasm, Unusual.Wasm similar to .NET 8 and UNO 5.1 - but apparently it doesn't.

What am I doing wrong?

but it's not clear why (we do not repro).

Is there additional info I could provide?

[jeromelaban]

That's what I though @jeromelaban. However, as per LinkerConfig.xml snippet above I thought the linker would just leave my 3 assemblies Unusual.Common, Unusual.Gui.Wasm, Unusual.Wasm similar to .NET 8 and UNO 5.1 - but apparently it doesn't.

It's not, but I don't have guidance to provide here, this is a linker behavior.

Is there additional info I could provide?

A binlog would help.

[DierkDroth]

Thanks @jeromelaban

It's not, but I don't have guidance to provide here, this is a linker behavior.

hmm ... so I understand:

• previously (.NET8) UNO was controlling the linker behavior by LinkerConfig.xml
• now (.NET 9) UNO no longer controls the linker behavior (since it falls in MS's court?!?) and it's not clear if LinkerConfig.xml has any relevance or not?
  Am I understand this correctly?

A binlog would help.

Does the binlog here help?

[jeromelaban]

now (.NET 9) UNO no longer controls the linker behavior (since it falls in MS's court?!?) and it's not clear if LinkerConfig.xml has any relevance or not?

The linker is controlled by LinkerConfig.xml, but the warnings are still raised. It's not a behavior we can change.

[DierkDroth]

The linker is controlled by LinkerConfig.xml, but the warnings are still raised. It's not a behavior we can change.

I see. So my 3 assemblies (and others in LinkerConfig.xml as well) are in fact excluded - it's just that (useless and confusing) warnings would be thrown for even excluded assemblies, correct?

[DierkDroth]

Also: further down the error stack I see this error
LinkerConfig.xml(11,3): warning IL2007: Could not resolve assembly 'Microsoft.Extensions.Options'.

I suspect this is related to the respective line in the LinkerConfig.xml file (below). Could that line be removed safely? Or needed it to be replaced by something else?

<linker>
	<assembly fullname="Unusual.Common" />
	<assembly fullname="Unusual.Gui.Wasm" />
	<assembly fullname="Unusual.Wasm" />

	<assembly fullname="System.Core">
		<!-- This is required by JSon.NET and any expression.Compile caller -->
		<type fullname="System.Linq.Expressions*" />
	</assembly>

	<assembly fullname="Microsoft.Extensions.Options" />
	<assembly fullname="System.Runtime" />
	<assembly fullname="System.Threading" />
</linker>