Unable to reuse TempTable created when also sending params into the execute

If you add a param in the same call that creates the temp table then the temp table won't be accessible in future calls. This is a very strange behavior we came across today.

This works fine:

connection.Open();

await connection.ExecuteAsync(
@"create table #foo (val int not null);
insert #foo (val) values (123)");

await connection.ExecuteAsync(@"insert #foo (val) values (111)");
var vals = await connection.QueryAsync<int>(@"select * from #foo");

This fails. The error is that the temp table #foo doesn't exist.

connection.Open();
await connection.ExecuteAsync(
@"create table #foo (val int not null);
insert #foo (val) values (@InsertDate)", param: new { InsertDate = insertDate2 });

await connection.ExecuteAsync(@"insert #foo (val) values (111)");
var vals = await connection.QueryAsync<int>(@"select * from #foo");

Start by reproducing the two ExecuteAsync sequences from the issue against the Dapper API, comparing the parameterized and non-parameterized cases. Trace the execution path used when params is supplied and verify that the temporary table remains available to subsequent calls; done means both examples can insert and query #foo successfully.