Start Debugging

Tag: native-aot

22 posts · Page 2 of 3

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.

2026-07-09 dotnet trimming native-aot

What is trim-safe code and how do I write it?

Trim-safe code is code the .NET trimmer can statically prove is reachable, so it survives when unused code is removed from a self-contained app. This is the practical guide: turn on the analyzer, drive every IL2xxx warning to zero, annotate reflection with DynamicallyAccessedMembers, propagate RequiresUnreferencedCode to public APIs, and replace unanalyzable patterns with source generators.

2026-06-20 dotnet trimming native-aot

What is the DynamicallyAccessedMembers attribute?

DynamicallyAccessedMembers tells the .NET trimmer and AOT compiler which members of a Type you reach by reflection, so they are kept instead of trimmed away. It turns a silent runtime MissingMethodException into a build-time IL2070 warning. Here is what the attribute does, how the data-flow analysis behind it works, and how to annotate parameters, fields, and generic type parameters correctly.

2026-06-19 dotnet native-aot performance

What is Native AOT and what does it cost you?

Native AOT compiles your .NET app to a single self-contained native binary with no JIT, buying fast startup and a small memory footprint. The price is a C toolchain at build time, slower publishes, per-RID builds, no reflection or Reflection.Emit, mandatory trimming, and no Dynamic PGO. Here is the full ledger.

2026-06-03 dotnet performance native-aot

.NET 11 Raises the Minimum CPU Baseline to x86-64-v2

.NET 11 Preview 4 drops support for pre-2013 x86/x64 chips and bumps the JIT baseline to x86-64-v2. Here is what breaks, why, and how to check your hardware before you upgrade.

2026-05-22 comparison dotnet native-aot

Native AOT vs ReadyToRun vs JIT in .NET 11: which should you ship?

Plain JIT with Dynamic PGO wins steady-state throughput, ReadyToRun cuts startup with zero code changes, and Native AOT gives the smallest, fastest-starting binary at the cost of reflection and dynamic code. Pick by deployment shape, not raw benchmarks.

2026-05-10 errors csharp dotnet

Fix: PlatformNotSupportedException: Operation is not supported on this platform in Native AOT

Native AOT strips the JIT and the interpreter, so reflection emit, expression-tree compilation, and unseen MakeGenericType throw at runtime. Find the call via IL3050 and replace it with a source generator or a pre-baked path.

2026-04-27 aws aws-lambda dotnet-11

How to reduce cold-start time for a .NET 11 AWS Lambda

A practical, version-specific playbook for cutting .NET 11 Lambda cold starts. Covers Native AOT on provided.al2023, ReadyToRun, SnapStart on the managed dotnet10 runtime, memory tuning, static reuse, trim safety, and how to actually read INIT_DURATION.

2026-04-27 csharp dotnet dotnet-11

How to use Native AOT with ASP.NET Core minimal APIs

A complete .NET 11 walkthrough for shipping an ASP.NET Core minimal API with Native AOT: PublishAot, CreateSlimBuilder, source-generated JSON, the AddControllers limitation, IL2026 / IL3050 warnings, and EnableRequestDelegateGenerator for library projects.

2026-04-24 dotnet dotnet-10 ubuntu

.NET 10 on Ubuntu 26.04: resolute Container Tags and Native AOT in the Archive

Ubuntu 26.04 Resolute Raccoon ships with .NET 10 in the archive, introduces -resolute container tags to replace -noble, and packages Native AOT tooling via dotnet-sdk-aot-10.0.