Can't Get SQL Debugger to Work

  • Thread starter Thread starter Colin
  • Start date Start date
C

Colin

Though I've enabled SQL Debugging for the project, I
can't get the debugger to stop at my breakpoints within a
stored procedure. What must I do/re-configure?

Of note is that I recently ran IIS lockdown.
 
I did all of that, but still haven't noticed any change.

I DID figure out that I can step into the stored
procedure directly (via the server explorer) but I
couldn't step into it (via SqlCommand.ExecuteScalar()) or
get it to break during normal debugging.

Any other ideas?
 
So we can't go FROM TSQL TO a VB.NET program but we should be able to go
FROM VB.NET TO TSQL right with step through--we always have. That's what
he's trying to do.

--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
MVP, hRD
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
 
Bill is right about what I'm looking for.
-----Original Message-----
So we can't go FROM TSQL TO a VB.NET program but we should be able to go
FROM VB.NET TO TSQL right with step through--we always have. That's what
he's trying to do.

--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
MVP, hRD
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________

cannot use Step Into to
go Managed Extensions
for


.
Click to expand...
 
Hi Colin,

I'm not quite sure about why this happens. If you follow the steps in MSDN,
the debugger should work. Would you please retry it?

Kevin Yu
=======
"This posting is provided "AS IS" with no warranties, and confers no
rights."
 
Hi Colin,

You can also check the settings for the break points.

Kevin Yu
=======
"This posting is provided "AS IS" with no warranties, and confers no
rights."
 
I'll try it out. Of note is that my copy of VS.NET EA
actually "upgraded" an old academic copy, and my instance
of SQL Server is still the version that came with MS
Office XP AE (I have a developer license copy, but I
haven't replaced the old copy yet). I wonder if that has
something to do with it.

I also recently ran IIS lockdown, which changed a few
configurations.

Then again, I'm probably just missing something stupid or
skipping a step. That's usually what happens.

Thanks for your help!
 
You're welcome, Colin. Thank you for sharing your experience with all the
people in the newsgroup.

Merry Christmas and happy new year!

Kevin Yu
=======
"This posting is provided "AS IS" with no warranties, and confers no
rights."
 
Back
Top