Why FluentMap?
Required package:
Dapper.FluentMap
Problem solved
Section titled “Problem solved”Separate database naming from clean, strongly typed domain models.
When to use it
Section titled “When to use it”Use this capability when the column shape and .NET model should remain separated by explicit, reviewable configuration.
Example
Section titled “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
Section titled “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.