scenario: asp.net WebForms + c# code behind + SQL server 2005 (via stored procedures invoked through a c# data access layer).
debug.writeline can create output that can be trapped by Mark Russinovich's DebugView utility: http://technet.microsoft.com/en-us/sysinternals/bb896647.aspx
DebugView greatly speeds up the debugging process because it's less necessary to actually step through multiple layers of asp.net webforms silliness with vs2008 in debug mode. if fact, vs2008 in many cases does not even need to be open at the time of debugging.
However, the problem arises when the data access layer passes control to a SQL stored procedure. Specifically, if something goes wrong within the stored procedure, even T-SQL PRINT statements will NOT be captured by DebugView AFAIK.
What strategies and/or techniques exist for effectively debugging vs2008 and its interactions with SQL Server 2005?
MORE INFORMATION
AFAIK, Microsoft has not made debugging easy when SQL Server 2005 stored procedures are involved at the same time with vs2008 c# and asp.net webforms.
Any ideas?
thnx/g.