I am getting a SQL Update error when trying to update a table by passing in an object to Dapper Contrib (I'm allowing it to map the object's properties to the database table):
Without running some kind of SQL Server profiling tool, can I see the generated SQL within Visual Studio debugger - or expose it somehow? This would greatly increase the speed of debugging.
I have found pieces about running MiniProfiler - I can get it working but it's only giving me the speed of something - not SQL - I went far into the weeds on that and I'm not even sure it's the right approach.
What's the best / simplest / quickest approach here just to see what SQL is being generated & to debug it?
I just ended up using SQL Profiler built into SQL Server. Simple easy solution.