dotnet-aot-compat

IL2070 occurs when reflection is called on a Type parameter lacking annotations. Add [DynamicallyAccessedMembers] with the required member types (e.g., PublicMethods) to the parameter, then cascade matching annotations outward to all callers.

Create a JsonSerializerContext with [JsonSerializable] attributes for each type you own, then replace JsonSerializer.Serialize(obj) and Deserialize<T>(json) calls with overloads taking MyContext.Default.TypeName. This removes reflection-based serialization warnings IL2026 and IL3050.

The pragma hides warnings from the Roslyn analyzer at build time, but the IL linker and AOT compiler still encounter the issue, causing failures at trim or publish time. Fix the underlying annotation flow or use [RequiresUnreferencedCode] instead.

The trim and AOT analyzers require net8.0 or later, so apply IsAotCompatible with a TFM condition for multi-targeting projects. For older TFMs, add a polyfill defining DynamicallyAccessedMembersAttribute locally since the trimmer recognizes it by name.

Use [RequiresUnreferencedCode] only as a last resort when a method fundamentally requires arbitrary reflection that cannot be statically described, such as Assembly.Load by name. It propagates the requirement to all callers, marking the whole call chain trim-incompatible.

Do not add external types to your JsonSerializerContext since source generation only works for types you own. If the type implements IJsonModel<T> (common in Azure SDK), call its Write/Create methods directly; otherwise write a custom JsonConverter<T>.