.NET Native AOT
Comments discuss .NET and C#'s Native AOT compilation capabilities, including its ability to produce standalone native binaries without a runtime, fast startup times, lower memory usage, and historical evolution from Windows-only to cross-platform support.
Activity Over Time
Top Contributors
Keywords
Sample Comments
Weren't .NET and its APIs originally Windows-only and they only became portable later? And doesn't .NET have AOT support?
C# recently came out with Native AOT (ahead of time) compilation that compiles your app to a binary that can run without the .NET runtime (!!), and has fast startup and lower memory overhead. There are a few drawbacks: many reflection and run-time code generation and loading features are unavailable, and LINQ expressions must be interpreted which makes them slow. But it's easy to work around those limitations for a greenfield infra project, and C# has great performance characteristics.
.NET also has AOT compilation, which HNers seem to keep forgetting about.
Curious to see how .NET Native would compare given it is using the same backend as VC++ .
Native AOT exists, and C# has many C++ like capabilities, so not at all.
That's no longer true with Windows 10 where .Net Native compiles everything into native code directly
.NET supports native AOT for a while now.
Have a look at CoreRT and Mono AOT
C# can be natively compiled, doesn't it?
You're behind the times:> Publishing your app as Native AOT produces an app that's self-contained and that has been ahead-of-time (AOT) compiled to native code. Native AOT apps have faster startup time and smaller memory footprints. These apps can run on machines that don't have the .NET runtime installed.https:/