Not stepping into library assembly

  • Thread starter Thread starter Bill McCormick
  • Start date Start date
B

Bill McCormick

I'm working on a project that has more than one assembly/dll. The debugger
will *step into* most of them but, but there is one that it won't step into.
Everything is being built under debug, and all the pdb files are present in
the output debug/bin folder.

Under Tools/Options/Debugging, *Enable Just My Code" is unchecked and
*Enable .NET Framework source stepping* is checked. Should I be able to
*step into* other assemblies (especially my own assemblies) that are part of
the solution *without* having to copy the assembly to the GAC?

TIA,

Bill
 
I'm working on a project that has more than one assembly/dll. The debugger
will *step into* most of them but, but there is one that it won't step
into. Everything is being built under debug, and all the pdb files are
present in the output debug/bin folder.

Under Tools/Options/Debugging, *Enable Just My Code" is unchecked and
*Enable .NET Framework source stepping* is checked. Should I be able to
*step into* other assemblies (especially my own assemblies) that are part
of the solution *without* having to copy the assembly to the GAC?
Click to expand...

Is the other assembly a project in your solution or did you merely reference
it by browsing for its DLL? In my experience, the IDE only wants to debug
projects that are in the solution.
 
Is the other assembly a project in your solution or did you merely reference
it by browsing for its DLL? In my experience, the IDE only wants to debug
projects that are in the solution.
Click to expand...
Yes, sorry. The DLL in question is both referenced and part of the solution.
 
Does your client have a dll, GAC, or project reference? If the DLL is in
your solution, you may want to try a project reference if you are not
already.
 
Does your client have a dll, GAC, or project reference? If the DLL is
in your solution, you may want to try a project reference if you are not
already.
Click to expand...

I should need to copy the assembly to the GAC if the project is part of the
solution, right? So, yes, the assembly/DLL is part of the solution and a
reference exits in all other projects/assemblies that use it.
 
I should need to copy the assembly to the GAC if the project is part of
the solution, right? So, yes, the assembly/DLL is part of the solution
and a reference exits in all other projects/assemblies that use it.
Click to expand...

Sorry, should NOT need to copy ...
 
Correct: should NOT.
Click to expand...

I found the problem:

I had a object that I was serializing built from a classes that were
decorated with [System.Diagnostics.DebuggerStepThroughAttribute()]

Thanks.
 
Back
Top