-
Notifications
You must be signed in to change notification settings - Fork 4.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
dotnet publish --native #51829
Comments
I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label. |
Please see our .NET 6 theme for our native AOT experiment. dotnet/runtimelab#248. You can track its progress in https://github.com/dotnet/runtimelab/tree/feature/NativeAOT. During .NET 6 we do not plan on adding this as an official option, but we are gathering data for potentially adding in a future release. |
It's a common false sense about performance that "being native will increase performance". .NET Already executes in native. Publish in native will only improve startup performance, which can be improved by R2R. |
Thanks @huoyaoyuan for the call out to R2R. Here is the documentation on publishReadyToRun: https://docs.microsoft.com/en-us/dotnet/core/deploying/ready-to-run |
I'm very unhappy because of performance talks about .net core. Most of people says that .net core is slower than Go and Java. I love .NET Core because it has perfect syntax and better IDE support. So I have to recommend this.
Please add --native option to "dotnet publish" command. It should be easy to publish and deploy .net native web apps to have faster response times than Go and Java.
Also please add .net native support to Azure and Azure Pipelines.
The text was updated successfully, but these errors were encountered: