Native AOT promises the holy grail for modern cloud deployments: lightning-fast startup times and a drastically reduced memory footprint. But trading the JIT compiler for Ahead-of-Time compilation isn't just a checkbox in your .csproj file—it is a fundamental shift in how your C# code executes. If you approach AOT blindly, the compiler will break your build, and your third-party libraries will fail silently at runtime.

This session bypasses the marketing hype and dives straight into the brutal technical realities of moving existing .NET services to Native AOT. We will systematically deconstruct the architectural limitations of an environment with no dynamic code generation and no runtime reflection. You will leave with a clear engineering roadmap, knowing exactly how to audit your codebase, spot AOT landmines before they blow up, and write AOT-compatible C# by default.

What You Will Learn:

🛑 The Breaking Limitations: Why dynamic reflection, heavy dependency injection, and runtime expression trees are completely incompatible with AOT.

🪤 NuGet Pitfalls & Trim Warnings: How to identify hidden, trim-incompatible dependencies in your library ecosystem and read compiler warning maps effectively.

🔧 The Mitigation Playbook: Practical techniques for replacing runtime reflection with modern C# compile-time source generators, specialized JSON serialization, and static dependency injection patterns.

📋 The "Go/No-Go" Checklist: A definitive framework to help your team evaluate if a service is a prime candidate for Native AOT, or if it should remain on the classic JIT runtime.

Stop fighting the compiler. Come learn the playbook to survive the migration without deep-tissue scarring!