Errors testing Dapper.Contrib when used with the Dapper.StrongName pacakge.

Using Dapper.Config with Dapper.StrongName causes the following error in Dapper.Tests.Config

CS0121 The call is ambiguous between the following methods or properties: 'Dapper.SqlMapper.QueryAsync<T>(System.Data.IDbConnection, string, object, System.Data.IDbTransaction, int?, System.Data.CommandType?)' and 'Dapper.SqlMapper.QueryAsync<T>(System.Data.IDbConnection, string, object, System.Data.IDbTransaction, int?, System.Data.CommandType?)' Dapper.Tests.Contrib (netcoreapp3.1) C:\Pub\Pulls\Dapper\Dapper.Contrib\tests\Dapper.Tests.Contrib\TestSuite.Async.cs 107 Active

Removing the Dapper.SqlBuilder from Dapper.Tests.Config brings up the following error:

CS0246 The type or namespace name 'SqlBuilder' could not be found (are you missing a using directive or an assembly reference?) Dapper.Tests.Contrib (netcoreapp3.1) C:\Pub\Pulls\Dapper\Dapper.Contrib\tests\Dapper.Tests.Contrib\TestSuite.Async.cs 238 Active

Start with Dapper.Contrib/tests/Dapper.Tests.Contrib/TestSuite.Async.cs at lines 107 and 238, then inspect how Dapper.Config, Dapper.StrongName, and Dapper.SqlBuilder are referenced by the test project. Reproduce the reported compiler errors and verify that the tests compile with a single QueryAsync method and a resolvable SqlBuilder type.