ZeroSharp is done by the same person as bflat (me). These ZeroSharp samples get broken all the time because they bend the MSBuild targets that ship with .NET to an extreme. Bflat is a more supportable route and has a couple extra customizations to the compiler specifically for these scenarios.

Except that isn't NativeAOT as it ships on the box using dotnet publish workflow, rather a curated workflow which requires special steps as shown on the efi-runtime example.

My remark was regarding the support you get with dotnet publish for NativeAOT, which by the way still doesn't support the GUI/EF scenarios from .NET Native.