I have learned that you can debug by stepping into stored procedure (SP) code in VS 2005 from your .NET code. This great feature allows you to watch line by line the execution of both your .NET code and SP code that you are calling from your .NET code.

If you don't know what I mean here is an example. You are debugging your .NET application line by line. Then when you execute the line that calls the SP, your debugger jumps into the stored procedure being called (if you have set a break point in that SP) and you can debug the stored procedure line by line just like .NET code. And then you can even return back to the .NET code debugging after the last line of that SP has executed if you have another break point in the .NET code following the call that executed the SP.

The only problem is that I was not able to do this with Dotnetnuke. I was only able to do it through a simple VB.NET web application using the following method to call the stored procedure:

SqlDataReader myReader = myPR.ExecuteReader();

I am wandering why I can't jump into stored procedure code from my DNN website. Would it have something to do with the fact that the data access layer-ed way of DNN calls stored procedures in a different way (using the SqlHelper class)?

Return CType(SqlHelper.ExecuteReader(ConnectionString, GetFullyQualifiedName("GetDetail"), Param1, Param2), IDataReader)

Please help me and help this community if you know the answer! Thanks!