What is wrong with debugger?

[Brett Romero]

I have a line of code that references a method in a .NET DLL. I can
usually debug into this DLL and step through the method. With a recent
update of the DLL (from some one else), I can't step into this method.
I hit the line in my app, try to step into it and the debugger seems to
go into the ether. No yellow highlighting anywhere. The app also
freezes.

What may be causing the debugger to behave this way?

Thanks,
Brett

 

[Chris Dunaway]

Did you get both an updated .dll and the .pdb file to go with it?
Also, does your app need to be recompiled with the new .dll version?

 

[Ignacio Machin \( .NET/ C# MVP \)]

Hi,

I have a line of code that references a method in a .NET DLL. I can
usually debug into this DLL and step through the method. With a recent
update of the DLL (from some one else), I can't step into this method.
I hit the line in my app, try to step into it and the debugger seems to
go into the ether. No yellow highlighting anywhere. The app also
freezes.

Was the dll compiled in debug mode? , do you have the pdb file of it?

 

[Brett Romero]

The missing pdb file was part of the problem. I step into the DLL. It
references a method in another DLL. When I try to step into that
method, I go into the disassembler. What is causing that?

It did initially popup some box asking if I wanting to view the
disassembler. I clicked yes by accident but also checked not to show
the box again. Now I can't get out of the disassembler when I step
into the method.

Thanks,
Brett

 

[Ignacio Machin \( .NET/ C# MVP \)]

Hi,

The missing pdb file was part of the problem. I step into the DLL. It
references a method in another DLL. When I try to step into that
method, I go into the disassembler. What is causing that?

You have no source for that second DLL , IIRc there is an option in the IDE
to do not follow to assembly, don't remember where it's right now
Ok, found it, it;s in Tools/Options/ Debugging/ "show disassembly if source
it not available."

 

[Brett Romero]

Thanks Ignacio. I found the option in Studio.

My problem was first not having the PDBs for each DLL but then I
started getting an error on compiles. Something to the affect of can't
build to output directory. Can't create assembly because file is in
use. I read on the boards that it occurs often and there isn't a
straight forward solution. Called MS to get the hotfix, which I had no
faith in. While on the phone with them doing troubleshooting, I
figured out the problem. Project1 is a library. I had a reference to
Project1.DLL in the actual project. Now the error makes sense. I
didn't reference the DLL that is produced on each build. Instead I was
referencing a version of Project1.dll in another location. That didn't
matter though. Adding that DLL was a complete oversight on my part.

There was some rearranging of DLL locations that morning. I scooped up
a bunch of .NET DLLs that are used in this project. Project1.DLL
happened to be in that group.

Brett