Frans, I was not sure where to put this. But could you add this to the how to section. Right now for adapter, I'm trying to figure out how to do this by looking back at previous post. Have yet to find the exact answer. I belive you added logging functionality for the next release, but having this info I could quickly step through a specific method. Thanks.

P.S. Could you let me what is the best way to do this for adapter?

erichar11 wrote:

Frans, I was not sure where to put this. But could you add this to the how to section. Right now for adapter, I'm trying to figure out how to do this by looking back at previous post. Have yet to find the exact answer. I belive you added logging functionality for the next release, but having this info I could quickly step through a specific method. Thanks.

P.S. Could you let me what is the best way to do this for adapter?

The best way in adapter is to derive a class from DataAccessAdapter and override On<action>() and On<action>Complete() methods, which receive an IQuery based object, which contains the query generated.

In 1.0.2004.2, I've added a fine grained tracing framework which allows you to simply add a few lines to the .config file and you'll get the query text delivered to the vs.net output window (or to a logfile if you add a trace listener already available to you in the .NET framework).

There is an SqlLogger template available in the 3rd party section too.