Dapper.FluentMap 3.4.0

Dapper.FluentMap 3.4.0 expands the maintained 3.x line with first-class multi-mapping, asynchronous multiple-result-set APIs, stricter generated materialization, broader database-provider certification, and a hardened release supply chain.

This release keeps the core packages on netstandard2.0 while substantially increasing the behavior validated by the project's automated compatibility matrix.

Highlights

FluentMap-controlled multi-mapping

FluentMap now provides first-class two-type multi-mapping through:

QueryMapped<TFirst, TSecond, TReturn>(...)

The API supports:

• splitOn boundaries;

• per-segment mapping profiles;

• immutable objects;

• nested mappings;

• value objects;

• property converters;

• Dapper TypeHandler interoperability;

• isolated FluentMapRuntime configuration.

LEFT JOIN scenarios are also handled so an absent child segment can be represented correctly instead of materializing an invalid object.

Async multiple-result-set materialization

The mapped multiple-result API now includes asynchronous counterparts:

QueryMultipleMappedAsync(...)
ReadMappedAsync<T>(...)
ReadMappedSingleAsync<T>(...)
ReadMappedSingleOrDefaultAsync<T>(...)

MappedGridReader preserves ordered result-set consumption and now rejects concurrent reads deterministically, while supporting cancellation and predictable disposal behavior.

Strict generated materialization

Applications that want to avoid runtime materialization fallback can now opt into a generated-only path using:

UseStrictGeneratedMaterialization()
QueryGeneratedMapped*()

Unsupported shapes fail deterministically instead of silently falling back to reflection-based runtime materialization.

Generated materializers also support safe permutations of distinct result columns, improving generated-path coverage for projections whose column order differs from the registered shape.

A dedicated Native AOT smoke test validates the strict generated SQLite path on win-x64.

Full Native AOT compatibility is not claimed. Reflection-based assembly scanning, arbitrary runtime fallback, and other dynamic scenarios remain outside the supported Native AOT boundary.

Provider certification

Provider compatibility is now continuously validated against real database instances in CI.

The SQL Server, PostgreSQL, MySQL, and MariaDB lanes are mandatory and fail closed when the database service or test configuration is unavailable.

These tests exercise mapped reads, generated/runtime materialization, multiple result sets, streaming, and relevant Dommel persistence scenarios.

Dapper compatibility

The supported Dapper range is now consistently defined and tested as:

Dapper [2.1.79, 3.0.0)

The CI matrix validates both:

• minimum supported: 2.1.79

• latest stable: 2.1.89

This aligns package metadata, documentation, and the versions exercised by CI.

Package family

The 3.4.0 release contains:

• Dapper.FluentMap

• Dapper.FluentMap.Dommel

• FluentMap.DependencyInjection

• FluentMap.Analyzers

• FluentMap.Generators

The FluentMap.* names are NuGet PackageIds only. Assemblies, namespaces, and public APIs remain under Dapper.FluentMap.*.

All packages continue to target netstandard2.0.

Release and supply-chain hardening

The release pipeline now provides stronger artifact verification and provenance, including:

• CodeQL analysis;

• dependency review gates;

• deterministic package inventory;

• SHA-256 checksums;

• SPDX 2.3 SBOM generation;

• GitHub artifact attestations;

• release artifact manifest;

• consumer smoke tests;

• validation of existing NuGet artifacts before publication;

• governed publication to NuGet.org and GitHub Packages.

Release and recovery workflows have also been aligned with the repository's main branch.

Compatibility notes

The historical static APIs remain available, including:

FluentMapper.Initialize(...)
EntityMap<TEntity>
Map(...).ToColumn(...)
Ignore()

For applications that need isolated FluentMap configuration, prefer FluentMapConfigurationBuilder and FluentMapRuntime.

The following remain intentionally outside the current compatibility claims:

• Dapper versions outside [2.1.79, 3.0.0);

• Dommel versions outside [3.5.3, 4.0.0);

• full Native AOT compatibility;

• per-runtime isolation of Dommel's global configuration;

• three-or-more-type multi-mapping;

• graph aggregation;

• CRUD generation.

Upgrade from 3.0.x

Existing applications using the historical FluentMap APIs can continue using them.

When upgrading, keep all FluentMap packages on the same release version and review the newer APIs only where they provide value to your application:

• use FluentMapRuntime when configuration isolation is required;

• use QueryMapped<TFirst,TSecond,TReturn> for FluentMap-controlled two-type multi-mapping;

• use QueryMultipleMappedAsync for asynchronous multiple-result processing;

• use strict generated materialization when deterministic generated-only behavior is required.

For applications consuming the auxiliary DI, analyzer, or generator packages, use the current PackageIds:

FluentMap.DependencyInjection
FluentMap.Analyzers
FluentMap.Generators

Thank you

Thanks to everyone who has used, tested, reported issues, reviewed changes, or contributed to the continued maintenance of Dapper.FluentMap.

Full changelog:
v3.0.3...v3.4.0

Dapper-FluentMap 3.0.3

This release focuses on stabilizing the FluentMap 3.x package family, improving Dommel mapping behavior, modernizing package distribution, and making the release pipeline significantly more reliable.

Highlights

Simplified NuGet package identities

Three supporting packages now use FluentMap-focused NuGet package IDs:

• Dapper.FluentMap.DependencyInjection → FluentMap.DependencyInjection
• Dapper.FluentMap.Analyzers → FluentMap.Analyzers
• Dapper.FluentMap.Generators → FluentMap.Generators

The core package identities remain unchanged:

• Dapper.FluentMap
• Dapper.FluentMap.Dommel

Only the NuGet package identities changed. Existing assembly names, namespaces, project identities, and public APIs are preserved.

For new installations:

dotnet add package Dapper.FluentMap --version 3.0.3
dotnet add package Dapper.FluentMap.Dommel --version 3.0.3
dotnet add package FluentMap.DependencyInjection --version 3.0.3
dotnet add package FluentMap.Analyzers --version 3.0.3
dotnet add package FluentMap.Generators --version 3.0.3

Fixes

• Fixed Dommel property resolution so FluentMap configuration remains deferred until the result is enumerated.
• Preserved the expected behavior when mappings are registered after ResolveProperties is called but before enumeration.

Maintainability

A broad internal refactoring reduced complexity across:

• core mapping validation;
• runtime materialization;
• analyzers;
• source generators;
• Dommel property/column resolution;
• release artifact validation.

These changes are internal and are intended to preserve existing public API and runtime behavior.

Packaging and tooling

• Modernized NuGet package metadata.
• Added and adopted the .slnx solution format while retaining the traditional .sln for compatibility.
• Updated Roslyn analyzer dependencies.
• Improved repository configuration and development tooling.
• Added stronger package metadata and release artifact validation.

Release reliability

The release infrastructure received substantial hardening in this version.

NuGet.org publication now treats package acceptance and package indexing as separate operations. All missing packages are submitted first, without blocking the package set while NuGet.org performs asynchronous validation and indexing.

After submission, the pipeline performs a bounded convergence phase and validates published primary package contents against the original release artifacts.

Release recovery is also resumable and idempotent, with safeguards for partially published releases.

Additional release safeguards include:

• NuGet Trusted Publishing through GitHub OIDC;
• independent symbol package publication;
• SHA-256 artifact verification;
• release manifests and dependency inventory;
• GitHub Packages publication;
• GitHub artifact attestations;
• package-content verification before skipping an already published version;
• protected recovery of incomplete releases without overwriting immutable packages.

Compatibility

No intentional public API breaking changes are introduced in 3.0.3.

Consumers of the Dependency Injection, Analyzer, or Generator packages should update their PackageReference to the new package IDs listed above.

Thanks to everyone using and contributing to Dapper-FluentMap. This release lays a stronger foundation for the FluentMap 3.x line, both for consumers and for future maintenance.

Full Changelog: v2.0.0...v3.0.3

Dapper.FluentMap

• Update to Dapper 2.0.35

Dapper.FluentMap.Dommel

• Update to Dapper.FluentMap 2.0
• Update to Dommel 2.0

Add conventions to the Dommel column name resolver

• Update Dapper to 1.60.1 - fixes #83
• Fix matching nullable properties in conventions - #82
• Don't fall back to default mapping when property is ignored - #81

• Use ReflectedType on full .NET and .NET Standard 2.0 (.NET Core 2.0 and .NET Core 2.1) for mapping properties from derived entities.
  • Fixes #42, #43 and #56
• Update Dapper to 1.50.5
• Releases Dapper.FluentMap.Dommel 1.6.0
  • Update Dapper to 1.50.5
  • Update Dommel to 1.10.1

• Update to .NET Core 2.0 SDK
• Update to .NET Standard library 1.6.1

Dapper.FluentMap.Dommel

• Release v1.5.0

• Fix mapping value objects - #58

v1.5.3

Compare

Choose a tag to compare

Update to .NET Core RTM

Migrated to .NET Standard 1.3

Version using Dapper v1.50.0-beta8