Question: Is there a way to dump the generated sql to the Debug log or something? I'm using it in a winforms solution so the mini-profiler idea won't work for me.

Answer: 
Dapper does not currently have an instrumentation point here. This is perhaps due, as you note, to the fact that we (as the authors) use mini-profiler to handle this. However, if it helps, the core parts of mini-profiler are actually designed to be architecture neutral, and I know of other people using it with winforms, wpf, wcf, etc - which would give you access to the profiling / tracing connection wrapper.

In theory, it would be perfectly possible to add some blanket capture-point, but I'm concerned about two things:

* (primarily) security: since dapper doesn't have a concept of a context, it would be *really really* easy for malign code to attach quietly to sniff all sql traffic that goes via dapper; I really don't like the sound of that (this isn't an issue with the "decorator" approach, as the caller owns the connection, hence the logging context)
* (secondary) performance: but... in truth, it is hard to say that a simple delegate-check (which would presumably be `null` in most cases) would have much impact

Of course, the other thing you could do is: steal the connection wrapper code from mini-profiler, and replace the profiler-context stuff with just: `Debug.WriteLine` etc.
Just to add an update here since I see this question still get's quite a few hits - these days I use either [Glimpse](http://getglimpse.com/) (seems it's dead now) or [Stackify Prefix](https://stackify.com/prefix/) which both have sql command trace capabilities.

It's not exactly what I was looking for when I asked the original question but solve the same problem.