Start Debugging

Tag: native-aot

21 posts · Page 1 of 3

2026-10-10 ef-core ef-core-11 dotnet-11

What Is a Compiled Model in EF Core 11, and When Is It Worth Enabling?

A compiled model is generated C# that recreates your EF Core model without running OnModelCreating. Measured on EF Core 11 RC1: model load drops from 714 ms to 215 ms at 500 entities, but the MSBuild route (which replaced EFOptimizeContext) is slower, stale models fail silently, and query filters block generation.

2026-10-07 vscode csharp dotnet-11

C# Dev Kit 11.0 Collapses Six Processes Into One Native AOT Binary

C# Dev Kit 11.0 pre-release replaces six managed processes with a single Native AOT CSDevKit process and a persistent project cache. A 407-project Aspire solution is ready in 3.0s instead of 84.1s, using 316 MB instead of 2,072 MB.

2026-09-10 errors ef-core ef-core-11

Fix: PublishAot plus EFOptimizeContext exhausts memory during an EF Core build

EF Core's build-time model generation re-entered MSBuild until RAM ran out. Upgrade Tasks and Design to 10.0.10+, and on EF Core 11 delete EFOptimizeContext.

2026-09-04 mstest native-aot testing

MSTest 4.4 Graduates the Reflection Source Generator, and Native AOT Projects Get It Automatically

MSTest 4.4 moves MSTest.SourceGeneration out of experimental and aligns it with the MSTest version. Native AOT test projects pick it up with no opt-in, ReflectionFree mode can now skip runtime discovery for plain [TestMethod] and [DataRow], and five AOTSG diagnostics tell you which test shapes will not survive.

2026-09-04 dotnet native-aot jit

What is the W^X flag in .NET and does Native AOT need it?

W^X (write xor execute) is the rule that no memory page is writable and executable at the same time. In .NET it is the DOTNET_EnableWriteXorExecute knob, on by default since .NET 7, and it exists entirely for the JIT. Native AOT never reads it. Here is how the runtime implements it, what it costs, and when turning it off is a legitimate fix.

2026-09-01 comparison dotnet dotnet-11

Framework-dependent vs self-contained vs Native AOT for a .NET 11 container image

Framework-dependent on a chiseled aspnet image is the right default for an ASP.NET Core service on .NET 11, because the runtime layer is shared across services and a runtime CVE is fixed by a base image bump. Self-contained trimmed and Native AOT buy a 2x to 5x smaller image and a much faster cold start, and cost you that. Real published sizes, the layer-sharing math, and the .NET 11 base image inference bug that breaks the AOT path.

2026-08-30 errors ef-core maui

Fix: Model building is not supported when publishing with NativeAOT in a .NET MAUI iOS build

iOS builds set DynamicCodeSupport=false, so EF Core refuses to build the model even though you never enabled NativeAOT. Ship a compiled model plus precompiled queries, or turn the interpreter back on.

2026-08-02 csharp dotnet dotnet-11

How to replace new Regex(...) with the [GeneratedRegex] source generator in .NET 11

A complete guide to converting new Regex(pattern, RegexOptions.Compiled) into [GeneratedRegex] in .NET 11: the mechanical rewrite, partial methods vs partial properties, measured startup and throughput numbers, the SYSLIB1040-1045 diagnostics, and the two patterns where the generator silently falls back to a cached Regex.

2026-07-29 errors csharp dotnet

Fix: Reflection-based serialization has been disabled for this application

This InvalidOperationException means PublishTrimmed or PublishAot flipped JsonSerializerIsReflectionEnabledByDefault to false. Fix it with a source-generated JsonSerializerContext.

2026-07-23 comparison aspnetcore dotnet-11

WebApplication.CreateBuilder vs CreateSlimBuilder vs CreateEmptyBuilder in ASP.NET Core 11

Use CreateBuilder for a normal app, CreateSlimBuilder when you publish trimmed or Native AOT behind a TLS proxy, and CreateEmptyBuilder only when you want to register every service yourself. Here is the feature matrix and the gotchas that force the call.