dotnet-aot-compat

Enable IsAotCompatible in the .csproj conditioned on net8.0 or later, then build and fix each IL analyzer warning iteratively. Add DynamicallyAccessedMembers annotations to reflection-based APIs and migrate JsonSerializer calls to a source-generated JsonSerializerContext.

Create a JsonSerializerContext with a JsonSerializable attribute for every type you own, then batch-update call sites to pass MyContext.Default.TypeName to Serialize and Deserialize. This replaces reflection-based serialization with source generation.

No. Pragma suppressions hide warnings from the Roslyn analyzer but the IL linker and AOT compiler still see the issue, so the code fails at trim or publish time. Use DynamicallyAccessedMembers annotations or RequiresUnreferencedCode instead.

The trim and AOT analyzers require net8.0 or later, so condition IsAotCompatible on the target framework. For older TFMs in multi-targeted projects, add a polyfill of DynamicallyAccessedMembersAttribute since the trimmer recognizes it by name.

Boxing a Type into object or object[] breaks the DynamicallyAccessedMembers annotation flow, so the trimmer loses track of required members and warns with IL2072. Refactor to pass the Type as a dedicated annotated parameter.

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 trim-incompatibility to all callers, so prefer annotation fixes first.