title: How to debug (step into) a class library referenced in my project and has .pdb and source code?
body: <p>When debugging the opened solution/project in Visual Studio (2015) I would like to debug (step into) a method call which is located in one of the referenced assemblies. The assembly has .pdb (copied local) and source code. This assembly actually is also my class lib project, but not in the current solution, instead in an other solution.</p>
  
  <p>I know the trivial solution to debug this assembly would be adding its project to the current solution instead of referencing it, then debugging experience would be seamless. However for some reasons this would not be too efficient in my case, for example there are <em>many</em> assemblies (dozens) which I should add and I do not want to end with a giant solution.</p>
  
  <p>What I've done/tried so far:</p>
  
  <ul>
  <li>I've unchecked Just my code</li>
  <li>I've checked that .pdb for the other assembly is copied to my current project's output folder.</li>
  <li>Tried to set a breakpoint just before the call, then step <em>into</em>. No success, the call was just stepped <em>over</em>.</li>
  <li>The assembly I would like to debug is coming as a NuGet package (not a simple browsed reference). Still true, it's my class lib project, comes with .pdb, and the source code is available in my local disk.</li>
  <li>Looked at Window->Debug->Modules: Symbol status: Symbols loaded. User Code: N/A. Symbol File location is a Temp Asp Files. (It is an ASP.NET MVC application)</li>
  <li>Because it is coming from a NuGet package its build is a Release build, but currently not optimized, and <em>has</em> the up to date .pdb</li>
  </ul>
  
  <p>As I recall this debugging feature was sometimes surprisingly worked automagically, however now it does not.</p>
  
  <p>What am I missing?</p>