-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Documentation for NativeAOT/precompiled queries #4868
Conversation
[.NET NativeAOT](/dotnet/core/deploying/native-aot) allows publishing self-contained .NET applications that have been compiled ahead-of-time (AOT). Doing so offers the following advantages: | ||
|
||
* Significantly faster application startup time | ||
* Small, self-contained binaries that have smaller memory footprints and are easier to deploy |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"Small" here is a relative term. Compared to FDD, it is orders of magnitude bigger.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What's FDD? :) Are you proposing to change "small" to "smaller"?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
FDD = Framework Dependent Deployment.
I would, personally and generally, avoid talking about binary size here. :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Comparing to FDD is a bit disingenuous, since you have to have the full .NET runtime installed, no? A hello world NativeAOT app is a few MBs, whereas the same thing with FDD is far bigger, if you count the runtime... Note that this mentions "small, self-contained", so if anything the comparison should be to SCD, where NativeAOT really is clearly much much smaller...
In any case, regardless of EF, smaller binary size is one of the main points of NativeAOT overall - it's certainly mentioned all around...
entity-framework/core/miscellaneous/nativeaot-and-precompiled-queries.md
Outdated
Show resolved
Hide resolved
entity-framework/core/miscellaneous/nativeaot-and-precompiled-queries.md
Outdated
Show resolved
Hide resolved
entity-framework/core/miscellaneous/nativeaot-and-precompiled-queries.md
Outdated
Show resolved
Hide resolved
entity-framework/core/miscellaneous/nativeaot-and-precompiled-queries.md
Outdated
Show resolved
Hide resolved
```console | ||
dotnet ef dbcontext optimize --precompile-queries --nativeaot | ||
``` | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'll add a link here to the MSBuild integration documentation in my PR
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OK. I've amended the docs to show adding the Tasks package rather than running dotnet ef dbcontext optimize
- in any case a link to the dedicated docs makes sense.
Closes #3988