Link to home
Start Free TrialLog in
Avatar of OddiC
OddiC

asked on

Why can I not step into any functions in my project???? ((F11 just steps over them))

Hi all,

I am trying to debug a project, however when I try to step into functions that are part of a referenced assembly, I am not able to step in (!!). The debugger simply steps over the funciton as if I had pressed F10.

Does anyone know why this might happen and how to correct it? The referenced assembly is strongly-named and is part of SourceSafe (the project I am debugging is also in SourceSafe).

Your help is greatly appreciated!!

-oddic
ASKER CERTIFIED SOLUTION
Avatar of ZachSmith
ZachSmith
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of OddiC
OddiC

ASKER

Dang. I went back and checked it was built in debug. I built again (both projects) in Debug mode, and still F11 is stepping over the referenced assembly's function calls.

....? I'm not sure what could be going on (I've debugged and stepped into this referenced assembly's functions many times before)
Like Zach mentioned, you have to make sure the assembly is built in DEBUG mode. On top of that you have to make sure that the [libraryName].pdb file exists in the directory with the referenced [libraryName].dll.
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
SOLUTION
Avatar of Fernando Soto
Fernando Soto
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Were you able to get it working?
Avatar of OddiC

ASKER

I have tried all of your suggestions, and, sadly no, I still am unable to debug the referenced assembly's functions...

I verified that the .pdb file is where it should be in the referenced assemby's directory. I am thinking there might be something up with my project that is preventing me from debugging normally.

I am going to try another project that references the same .dll and see if the problem exists in that scenario as well.

Thanks for all the insight so far! (I'm sure it's (the fix) something minor).
Weird.. You're building the current project in DEBUG too, right? I know sometimes I'll build in release on accident.
Avatar of OddiC

ASKER

Dangit- the issue seems to be with the ref'd assembly, I just tried another project and I have the same problem.

Avatar of OddiC

ASKER

Maybe this helps- I deleted the referenced .dll from my GAC, compiled AGAIN with Debug mode, and added it back to the GAC. I then recopiled the project that references the .dll, and attempted to debug. Strangely, it is now debugging the values associated in the function call (which are in the ref'd assembly) but it never gets to the actual function!!!

I think I'm going crazy. I'll try some other things, but if anyone can shed some light on what might be going on, I would be very, very grateful.

Thanks,

oddic
Avatar of OddiC

ASKER

I haven't a clue as to why.... but it is now working. I deleted all temp ASP.NET files, did an iisreset and now I can debug normally. There must have been some temp file that had the ref'd dll compiled as 'Release' or something. Thank you all for your help with this.

I will distribute points evenly to all who offered assistance.