Can we use emit on wasm with Mixed Interpreter and AOT Mode?

[SongOfYouth]

I have push the wasm app with:

    <WasmBuildNative>true</WasmBuildNative>
    <WasmShellEnableJiterpreter>true</WasmShellEnableJiterpreter>
    <WasmShellMonoRuntimeExecutionMode>InterpreterAndAOT</WasmShellMonoRuntimeExecutionMode>
    <JsonSerializerIsReflectionEnabledByDefault>true</JsonSerializerIsReflectionEnabledByDefault>

but the wasm app crashed when using emit eg. Castle.Core.

[jeromelaban]

Thanks for the report. Make sure to provide details of what crashes, where and when. A repro would be useful, as always :)

[SongOfYouth]

There is no any output,just stoped on the loading page.

[SongOfYouth]

My project has a deep logic dependency so that it's difficult to provider a clean demo, but i think it's the emit with 'AOT' problem. If remove the Castle.Core releated dynamic proxy logic, i works fine.

[SongOfYouth]

After my attempts, I found that emit is feasible in mixed mode. My problem is that a part of the assembly is missing from the link file.
Is there a way to know which assemblies are missing during the AOT process instead of just interrupting directly at runtime? even if the upper level logic related assemblies are already included in the link file, their dependent assemblies will still be pruned. @jeromelaban

[jeromelaban]

Thanks for the update, yes the linker links files out by default, particularly those that are not linker compatible. There's no direct way to determine which files are removed, other than reading the linker's output in a binlog.

Still, those errors should be surfaced as exceptions and there's likely some portion of the code that runs your app that is hiding exceptions.