ansaurus

Question

Answer 1

+1 A:

Make sure that the assembly you are referencing was built with a Program Database File for debugging purposes. If the debugging information is not present, this can happen.

Typically, if the library is part of the same solution, just make sure that all of the projects are being built in Debug. By default, Debug will generate the .pdb files required for debugging, as well as turn off the optimizations that can sometimes cause debugging difficulties.

Reed Copsey 2010-10-08 15:44:02

Thanks, so I checked and all projects were in Debug mode but still not sure how to see if the pdb file exists or not .

BDotA 2010-10-08 15:51:30

@BDotA: Have you tried just doing a full rebuild? THat will often fix this type of thing... However, the .pdb should be sitting next to the .dll/.exe in the bin\Debug (or bin\x86\Debug) folders [default paths]

Reed Copsey 2010-10-08 15:53:26

Thanks, Ok I checked all the things you mentioned. but still it cannot step into that method. so this method is in a library that is one of the projects I have included in my solution and one of the other projects in my solution is referencing and using it , so I did change the reference in the References section to point to this Project reference in the solution as well... I marked your answer as the correct answer because I think these are all the things we can check to fix this! However not fixed yet for me! Thanks for the help.

BDotA 2010-10-08 16:04:35

@BDotA: Make sure that the projects referencing it use the project, not the .dll, to add the reference, as well. That often helps...

Reed Copsey 2010-10-08 16:05:25

Ok, I could fix it but this problem is very annoying. The problem is that although I had changed all the references to their project refs but still it was loading it from the DLL version because Visual Studio looks at the first time that it is using that DLL. so ANOTHER dll in one of the projects was internally using it first so the fix is to ALSO INCLUDE ALL the lower level projects that are using that DLL and change their refs which usually it is even hard to know what to include. VB 6.0 was doing a MUCH BETTER job by only looking at our VBG projects. but VS.NET looks at the FIRST use time

BDotA 2010-10-08 21:31:41

@BDotA: Yeah, that's the problem - if you find it from a DLL, and it's a different build, you can't debug. You need to use project refs always, if possible.

Reed Copsey 2010-10-08 22:10:16

ansaurus

tags:

views:

answers:

Cannot debug into the code

related questions