How to publish AOT?
See original GitHub issueIf I publish the sample app, I still get a managed .NET dll file with an executable host file and all the .NET runtime dll files. But when I publish a console project with AOT I get a single unmanaged executable. This is what I’ve expected for Winforms as well.
I used this command dotnet publish -r win-x64
and then went to the publish
folder.
Issue Analytics
- State:
- Created a year ago
- Comments:21 (11 by maintainers)
Top Results From Across the Web
Native AOT deployment overview - .NET
Publish native AOT using the CLI · Add <PublishAot>true</PublishAot> to your project file. This property enables native AOT compilation during ...
Read more >Tutorial: Publish an ASP.NET Core app using native AOT
Learn about how to publish an ASP.NET Core app using native AOT.
Read more >Microsoft Intros Native AOT for ASP.NET Core
Microsoft Native AOT deployment guidance explains that native AOT support lets developers create a self-contained app, AOT-compiled to native ...
Read more >.NET functions with native AOT compilation - AWS Lambda
Learn how to create and deploy Lambda functions that use .NET 7 with native AOT compilation, which can reduce cold start times.
Read more >Ahead Of Time (AOT) Compilation To Native Code In .NET 7
NET development, we compile and build our code to Intermediate Language (IL). Then, when we run the application, the JIT (Just-In-Time) compiler ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Try