From d697f40887bd91ff7648f686d50ee1462b50ada9 Mon Sep 17 00:00:00 2001 From: dotnetdoktor Date: Wed, 13 Nov 2024 00:08:44 +0100 Subject: [PATCH] Fix: net ef dbcontext --> dotnet ef dbcontext --- .../core/performance/nativeaot-and-precompiled-queries.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/entity-framework/core/performance/nativeaot-and-precompiled-queries.md b/entity-framework/core/performance/nativeaot-and-precompiled-queries.md index 1ec493d3ac..18707fa573 100644 --- a/entity-framework/core/performance/nativeaot-and-precompiled-queries.md +++ b/entity-framework/core/performance/nativeaot-and-precompiled-queries.md @@ -50,7 +50,7 @@ You're now ready to publish your EF NativeAOT application: dotnet publish -r linux-arm64 -c Release ``` -This shows publishing a NativeAOT publishing for Linux running on ARM64; [consult this catalog](/dotnet/core/rid-catalog) to find your runtime identifier. If you'd like to generate the interceptors without publishing - for example to examine the generated sources - you can do so via the `net ef dbcontext optimize --precompile-queries --nativeaot` command. +This shows publishing a NativeAOT publishing for Linux running on ARM64; [consult this catalog](/dotnet/core/rid-catalog) to find your runtime identifier. If you'd like to generate the interceptors without publishing - for example to examine the generated sources - you can do so via the `dotnet ef dbcontext optimize --precompile-queries --nativeaot` command. Due to the way C# interceptors work, any change in the application source invalidates them and requires repeating the above process. As a result, interceptor generation and actual publishing aren't expected to happen in the inner loop, as the developer is working on code; instead, both `dotnet ef dbcontext optimize` and `dotnet publish` can be executed in a publishing/deployment workflow, in a CI/CD system.