title: How to debug a referenced dll (having pdb)
body: <p>I have two solutions in my workspace, say A and B.</p>
  
  <p>Solution A is an older project which I finished coding some time ago.
  In solution B, I need to use some classes from Solution A. To do so, I add a reference to the dll of one of the projects in solution A.</p>
  
  <p>The problem is when I try to debug. I want to be able to step into A's code as well. Visual studio is not able to load the code for these classes ("There is no source code available for the current location.") and I can only view the disassembly, which is not useful.</p>
  
  <p>The only way I know to debug classes from solution A is by running solution B, detach all processes (in the Debug menu item) and attach the process from solution A.</p>
  
  <p>However, this is very inconvenient and I can only debug A OR B at once.</p>
  
  <p>Is there a way to allow stepping into the code of referenced dlls (for which I do have the source code)?</p>
  
  <hr>
  
  <p><strong>Solution:</strong> My mistake was that I thought that a project can only be part of a single solution. In fact, a project can be part of any number of solutions.<br/>
  When you need to reference the old project, you should simply add the project to the solution. This is done by right clicking the new solution in the Solution Explorer > Add > Existing Project.<br/>
  Then, you'll be able to add the project reference. As others wrote, you should probably completely avoid using dll references to your own code (or other code you might need to change and debug).</p>
  
  <p>A very good reference to how solutions should be designed can be found in <a href="http://msdn.microsoft.com/en-us/library/bb668953.aspx" rel="noreferrer">MSDN</a>.</p>