[pjmlp]

Just like with Native AOT, as it only supports CLI, dynamic libraries with C ABI, and a special flavour of ASP.NET with minimal APIs introduced now in .NET 8.

Mono AOT supports a bit more, with focus on iOS and Android workloads.

None of them work with GUI frameworks or classical ASP.NET applications.

[neonsunset]

MAUI iOS can also be targeted by NativeAOT[0] and Avalonia has been proven to work with it as well.

Also, you can statically link NativeAOT libraries into existing C/C++/Rust/etc. code, and you can statically link existing static libraries into NativeAOT binaries[1].

[0] https://devblogs.microsoft.com/dotnet/dotnet-8-performance-i...

[1] https://github.com/lixinyang123/AvaloniaAOT

[2] https://learn.microsoft.com/en-us/dotnet/core/deploying/nati...

[pjmlp]

MAUI iOS with NativeAOT is experimental, and is still only of target out of many.

Avalonia is great, however the biggest issue is with Microsoft own tech, as many of us are well aware, many companies are Microsoft shops and only care about what is in the Visual Studio box.

There, not only is Native AOT behind .NET Native, there is no plan to ever support AOT in Forms and WPF projects.

On the libraries I stand corrected regarding static linking.