Dapper.DDD.Repository.Sql 1.8.1

dotnet add package Dapper.DDD.Repository.Sql --version 1.8.1
NuGet\Install-Package Dapper.DDD.Repository.Sql -Version 1.8.1
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package.
<PackageReference Include="Dapper.DDD.Repository.Sql" Version="1.8.1" />
For projects that support PackageReference, copy this XML node into the project file to reference the package.
paket add Dapper.DDD.Repository.Sql --version 1.8.1
#r "nuget: Dapper.DDD.Repository.Sql, 1.8.1"
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package.
// Install Dapper.DDD.Repository.Sql as a Cake Addin
#addin nuget:?package=Dapper.DDD.Repository.Sql&version=1.8.1

// Install Dapper.DDD.Repository.Sql as a Cake Tool
#tool nuget:?package=Dapper.DDD.Repository.Sql&version=1.8.1


This package provides support for using Dapper.DDD.Repository with MS SQL Server.


Install the package Microsoft.Data.SqlClient in your project. Then simply provide an instance of SqlQueryGenerator as your QueryGenerator, set your Schema and create a SqlConnectionFactory in your project, and you're done:

	options.ConnectionFactory = new SqlConnectionFactory("CONNECTIONSTRING");
	options.QueryGeneratorFactory = new SqlQueryGeneratorFactory();
	options.Schema = "dbo"; // Default schema, adjust if necessary

Also here's a simple SqlConnectionFactory you can use:

using System.Data;
using Dapper.DDD.Repository.Interfaces;
using Microsoft.Data.SqlClient;


internal class SqlConnectionFactory : IConnectionFactory
	private readonly string _connectionString;

	public SqlConnectionFactory(string connectionString)
		if (string.IsNullOrWhiteSpace(connectionString))
			throw new ArgumentException("connectionString cannot be null or whitespace.", nameof(connectionString));

		_connectionString = connectionString;

	public IDbConnection CreateConnection()
		return new SqlConnection(_connectionString);

Using Geometry and Geography

Dapper doesn't inherently play that well with these column types, however this package has a solution for it. In this example I'll use NetTopologySuite for my C# Geometry classes, but the principle is the same if you're using Microsoft's classes (or even some other third party).

The solution is actually rather simple: Serialize Geometry/Geography columns to binary, as this is supported by Dapper. To do so requires two configurations:

  • The SqlQueryGeneratorFactory needs to know which types to serialize in order to generate the proper SQL (which looks like this: ([dbo].[Table].[Column]).Serialize() AS [Column])
  • TypeConverters needs to be added for actually converting to/from binary

Here's an example of such a configuration for the Point type from NetTopologySuite - use the same approach for any other types:

	using NetTopologySuite.Geometries;
	using NetTopologySuite.IO;
	services.ConfigureDapperRepositoryDefaults(options =>
		options.QueryGeneratorFactory = new SqlQueryGeneratorFactory().SerializeColumnType(type => type.Namespace == "NetTopologySuite.Geometries"); // This ensure any Geometry type from NetTopologySuite gets serialized in the queries
		options.AddTypeConverter<Point, byte[]>(geo => new SqlServerBytesWriter() { IsGeography = false }.Write(geo), bytes => (Point)new SqlServerBytesReader() { IsGeography = false }.Read(bytes)); // Set IsGeography to true if you're using geography and not geometry

And that's basically it, now you can define properties of the type Point in any of your aggregates and the built-in ITableRepository will work correctly.

There are however still 2 caveats to look out for:

  • You need to remember to .Serialize() your column manually for your own queries, otherwise you'll get an exception similar to this: System.Data.DataException : Error parsing column
  • There is currently no way to support both geography and geometry of the same C# type simultaneously. This is because only a single TypeConverter can exist for a single type. A workaround might be to declare two classes yourself and use those instead like this:
	public class GeometryPoint : Point

	public class GeographyPoint : Point
	options.AddTypeConverter<GeometryPoint, byte[]>(geo => new SqlServerBytesWriter() { IsGeography = false }.Write(geo), bytes => (GeometryPoint)new SqlServerBytesReader() { IsGeography = false }.Read(bytes));
	options.AddTypeConverter<GeographyPoint, byte[]>(geo => new SqlServerBytesWriter() { IsGeography = true }.Write(geo), bytes => (GeographyPoint)new SqlServerBytesReader() { IsGeography = true }.Read(bytes));

Note: I haven't tested this approach myself, so it might not be that simple! It depends on whether the SqlServerBytesReader can deal with custom types or not.

Known issues with Geometry and Geography

These 2 exceptions will appear if you've missed one of the steps above:

  • System.Data.DataException : Error parsing column: You've not added .SerializeColumnType to your SqlQueryGeneratorFactory, it's not correctly detecting the type or you've forgotten to call .Serialize() in your own custom Query.
  • System.ArgumentException : An item with the same key has already been added. Key: Item: You've not added a TypeConverter for one or more of your C# geometry types.
Product Compatible and additional computed target framework versions.
.NET net8.0 is compatible.  net8.0-android was computed.  net8.0-browser was computed.  net8.0-ios was computed.  net8.0-maccatalyst was computed.  net8.0-macos was computed.  net8.0-tvos was computed.  net8.0-windows was computed. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

NuGet packages

This package is not used by any NuGet packages.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last updated
1.8.1 72 5/13/2024
1.8.0 133 1/16/2024
1.7.0 249 3/10/2023
1.6.1 2,062 10/30/2022
1.6.0 366 10/29/2022
1.5.1 1,182 8/30/2022
1.3.0 548 8/6/2022
1.2.0 395 8/4/2022
1.1.3 399 7/23/2022
1.1.2 441 7/13/2022
1.1.1 509 7/10/2022
1.1.0 396 7/10/2022
1.0.1 429 7/9/2022
1.0.0 447 7/9/2022