domains / families / software-engineering / aot-trimming

aot-trimming

separate

Guidelines for making .NET libraries and applications trimming-safe and Native AOT compatible. Covers the trimming/AOT model, the MSBuild properties that enable analysis (IsTrimmable, IsAotCompatible, PublishTrimmed, PublishAot), the trimming attributes (RequiresUnreferencedCode, RequiresDynamicCode, DynamicallyAccessedMembers, UnconditionalSuppressMessage), IL2xxx/IL3xxx warning codes, and a pattern playbook: source generators and UnsafeAccessor, generated-interception diagnostic suppressors, intentional runtime scanning boundaries, trimming-safe islands and feature switches, migration analyzers, and temporary warning-approval baselines. Use when introducing trimming/AOT support, resolving IL2xxx/IL3xxx warnings, or making reflection-heavy code trimming-safe in C# / .NET codebases. For System.Text.Json AOT scenarios, see also the serialization skill.

When to use

• Adding trimming (`PublishTrimmed`) or Native AOT (`PublishAot`) support to a library or application
• Resolving `IL2xxx` (trimming) and `IL3xxx` (AOT/single-file) warnings
• Making reflection-heavy code trimming-safe
• Replacing runtime reflection, assembly scanning, or `Reflection.Emit` with compile-time alternatives
• Reviewing a codebase or PR for trimming/AOT compatibility, including generated interceptors and analyzer suppressors
• Designing public APIs that must carry trimming annotations

When not to use

• System.Text.Json AOT scenarios

Skill page

Source