This is a grouping of related issues. Feel free to vote (👍) for this issue to indicate that this is an area that you think we should spend time on, but consider also voting for individual issues for things you consider especially important.

ILLinker allows making application size smaller by trimming code that isn't actually used. This is problematic in various dynamic/reflection scenarios, where the linker is unable to know that a method is actually needed.

Done in 8.0

• Allow stripping away all model building code to reduce application size #29755

Backlog

• When looking up methods via reflection, be trimming/AOT-friendly #26288
• Stop eagerly loading methods/members via reflection which aren't necessarily needed #27113
• Specifically check SQLite (i.e. the native dependency thing)
• Add feature switches to reduce app size #24901
• Allow stripping away the 1st part of the query pipeline to reduce application size #29762
• Consider removing the partial trimming annotations introduced in EF Core 7.0 #29763

Resources:

• .NET documentation on preparing libraris for trimming
• App Trimming in .NET 5
• Customizing Trimming in .NET 5

FYI the regression testing strategy for this isn't trivial
Relevant blog post: https://devblogs.microsoft.com/dotnet/app-trimming-in-net-5/