3 ms·
>and you still CAN'T build a AOT statically compiled single file executable, you have to ship your 300 DLLs with you, even that, they couldn't improve, it's 202
by HideousKojima 5y ago
>and you still CAN'T build a AOT statically compiled single file executable, you have to ship your 300 DLLs with you, even that, they couldn't improve, it's 2021, it's a billion dollar company, and yet, it's still "we are working on it", dude no, it's too late, i'll go with GO
I published a single file executable just last week, what in the world are you talking about? If there are any native code DLLs you have to include 1 extra line in your .csproj file to get those to be included in the single file, but other than that it works without any issues whatsoever. Literally spits out a .exe and a .pdb file and nothing else.
- pjmlp 5y agoWhich kind of AOT flavour? NGEN, .NET Native, the pseudo extract zip, the pseudo extract zip with mmap execution,..... https://github.com/dotnet/designs/blob/main/accepted/2020/form-factors.md#native-aot-form-factors https://github.com/dotnet/designs/blob/main/accepted/2020/fo... Even in .NET 6 it is going to be "almost there, wait a bit more for .NET 7 to cover all use cases". https://devblogs.microsoft.com/dotnet/announcing-net-6-preview-6/#comment-9721 https://devblogs.microsoft.com/dotnet/announcing-net-6-previ...
- HideousKojima 5y agoI was referring to the previous commenter's claim about publishing single file executables, not AOT compilation. AFAIK, true AOT compilation is still only possible with Mono, not .NET Core. Though the line between those is getting blurrier all the time now, since I'm pretty sure Mono is what is technically used if you publish a Xamarin app for iOS, even if you technically developed it in .NET Core/6.
- pjmlp 5y agoFair enough, although that is the whole problem with the .NET team and AOT. If I recall correctly they did at least three surveys asking us what did we mean by AOT compilation. Apparently they use another dictionary at Redmond, duh.