Sven Boemer

Interesting - this was using https://swaywm.org/.

I think we should simplify the third scenario to behave either identically to the second (as if PublishAot were set to true), or to not do an AOT publish at...

@jkurdek the runtime version issue is resolved now, and the new warnings are showing up.

@radical I tried to disable IL2121 in the wasm samples as well. Would you be able to do the same anywhere else that it needs to be disabled for wasm?...

Thanks - we're still trying to figure out why the reference was missing, but I thought I'd file the issue about the optimization as well.

Some more context: The unresolved reference in the case we hit looks like it was part of a code path that only lights up when an optional package is added...

I tried the repro as a `win-x64` console app and the descriptor you shared fixes deserialization, so this might be specific to the Xamarin SDK. I am not currently set...

Sorry for the delay - I wasn't able to see anything wrong from the binlog, which indicates that the descriptor is getting passed along correctly. @vitek-karas would your repro tool...

Would you be able to share a binlog or repro instructions of the case where it is warning even when NoWarn has IL2121?

I do see a few places where the `ILLink` task is being called directly without passing in the `NoWarn` argument: https://github.com/dotnet/aspnetcore/blob/197c1693d3c830af52b587e8d88891bc9689be44/src/Tools/LinkabilityChecker/LinkabilityChecker.csproj#L47-L55 https://github.com/dotnet/aspnetcore/blob/197c1693d3c830af52b587e8d88891bc9689be44/src/Components/WebAssembly/testassets/WasmLinkerTest/WasmLinkerTest.csproj#L49-L57 These invocations should probably do what the SDK...