4 ms·
C# supports dynamic loading in AOT compilation. Native AOT, and the oldie NGEN only do dynamic linking. https://learn.microsoft.com/en-us/dotnet/core/deployin
by pjmlp 1y ago
C# supports dynamic loading in AOT compilation.
Native AOT, and the oldie NGEN only do dynamic linking.
https://learn.microsoft.com/en-us/dotnet/core/deploying/native-aot/libraries https://learn.microsoft.com/en-us/dotnet/core/deploying/nati...
.NET Native can do both,
Applications are statically compiled, libraries are compiled into WinRT components, COM's evolution, introduced in Windows 8.
https://learn.microsoft.com/en-us/windows/uwp/dotnet-native/net-native-and-compilation https://learn.microsoft.com/en-us/windows/uwp/dotnet-native/...
Just watched the 2024 talk by the way, quite interesting.
- neonsunset 1y ago.NET Native is essentially dead. NGEN is specific to .NET Framework. It is possible to dynamically link multiple binaries with the same runtime with NativeAOT but it is very exotic and undocumented path that is not guaranteed to be stable. Not much worse than Go's dynamic linking which also requires the same compiler version.
- pjmlp 1y agoIn theory, in practice the almost resourless WinUI/WinAppSDK team is yet to change the minds of the few companies that believed in UWP to move away from it, due to the amount of missing features after 5 years of Project Reunion. In fact, the ones that care to port their applications might create Web versions than bother with Native AOT.