dotnet-aot-compat

Resolve IL2026 and IL2070 warnings by annotating reflection usage with DynamicallyAccessedMembers to preserve type information during trimming. This strategy enables iterative, warning-driven fixes without relying on unsafe suppressions, ensuring your .NET projects are Native AOT-compatible.

Making a .NET project trimming-safe involves enabling AOT analyzers for net8.0+ projects and iteratively fixing IL trim warnings. You must annotate reflection code flow with DynamicallyAccessedMembers and migrate JSON serialization to source generation to minimize reflective dependencies.

Yes, Native AOT compatibility requires upgrading your project target frameworks to net8.0+. You must enable IsAotCompatible in your project file and begin iterative fixes of IL trim warnings to ensure ahead-of-time compilation succeeds safely.

IL2072 and IL2067 warnings occur during AOT analysis because the trimmer cannot statically guarantee type members are preserved through reflection code flow. You fix these by applying DynamicallyAccessedMembers annotations to refactor the flow and satisfy the analyzer requirements.

Suppressing IL3050 warnings is discouraged for AOT compatibility. The recommended approach is to follow iterative, warning-driven fixes by annotating DynamicallyAccessedMembers and refactoring annotation flow, avoiding unsafe suppressions to maintain trimming safety.

Migrate JSON serialization to source generation to make .NET projects AOT-compatible. This minimizes reflective dependencies by providing compile-time type information, which works alongside DynamicallyAccessedMembers annotations to resolve IL trim warnings.