Trimming and Native AOT Limitations

Required package: Dapper.FluentMap

Problem solved

Use explicit or generated paths without claiming complete AOT support.

When to use it

Use this capability when the column shape and .NET model should remain separated by explicit, reviewable configuration.

Example

public sealed class CustomerMap : EntityMap<Customer>
{
    public CustomerMap()
    {
        Map(x => x.Id).ToColumn("customer_id");
        Map(x => x.Name).ToColumn("customer_name");
    }
}

How it works

FluentMap registers typed metadata and applies it through the matching materialization path. SQL, connections, parameters, and lifecycle remain responsibilities of the application and Dapper.

Constraints