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.
"Small" here is a relative term. Compared to FDD, it is orders of magnitude bigger.
There was a problem hiding this comment.
What's FDD? :) Are you proposing to change "small" to "smaller"?
There was a problem hiding this comment.
FDD = Framework Dependent Deployment.
I would, personally and generally, avoid talking about binary size here. :)
There was a problem hiding this comment.
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
Show resolved
Hide resolved
entity-framework/core/miscellaneous/nativeaot-and-precompiled-queries.md
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.
I'll add a link here to the MSBuild integration documentation in my PR
There was a problem hiding this comment.
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.
4 participants
Closes #3988