Fact is, there haven't been too many questions yet, but here are some of the more obvious ones from our own time working with SnapDAL
Here are some examples off things you can't do with parameterized queries:
<system.diagnostics> <switches> <add name="dfSwitch" value="1" /> </switches> <trace autoflush="true" indentsize="4"> <listeners> <add name="myListener" type="System.Diagnostics.TextWriterTraceListener" initializeData="myListener.log" /> </listeners> </trace> </system.diagnostics>This will turn on tracing which is then put in a the log file myListener.log. If you are running in visual studio, vs will display all trace output in the Output window of the ide with the Debug section selected. Tracing is not turned by default however because of the performance hit. Tracing is always used in the Mock.Util class because there is no downside to having it on during development.