Skip to content

Feature | Add trimming and AOT readiness validation lane #201

@AnnaSasDev

Description

@AnnaSasDev

Problem / Motivation

No explicit trimming/AOT metadata or validation lane exists for library readiness.

Proposed solution

Add trim/AOT CI builds, annotate dynamic/reflection-sensitive APIs, and define compatibility guarantees.

Alternatives considered

Defer until downstream app requests.

Use case

Consumers targeting startup/size-sensitive deployments in modern .NET.

Impact

Critical

Scope

No response

Possible implementation

CI matrix jobs with PublishTrimmed=true and AOT smoke tests.

Additional context

Helps .NET 8/9/10 forward-compatibility confidence.

Checklist

  • I searched existing issues
  • This is not a support question

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions