8

I have a c# solution A in my Visual Studio 2010. I have added a dll of solution B as a Reference. I have built solution B with "Debug".

If I run solution A in debug mode I can debug into solution B (Step Into F11) and see the code. That's nice. If I am NOT in debug mode and I "Go to definition (F12)" of external code Visual Studio opens a file without the body/logic of the methods :-( It looks something like an Interface.

Is it possible to "Go to definition (F12)" of external code in edit mode? Do I need a plugin?

I do not want to edit the external code. I just want to read the logic and set breakpoints.

Andhi Irawan
  • 456
  • 8
  • 15
koalabruder
  • 2,794
  • 9
  • 33
  • 40
  • Take a look at [Visual Assist](http://www.wholetomato.com/) – Dialecticus Oct 08 '12 at 12:31
  • Why not instead of adding the DLL, add the the project B to to Solution A and reference that instead ? – Nasreddine Oct 08 '12 at 14:08
  • 1. project B stands for more than one project. – koalabruder Oct 09 '12 at 08:43
  • If I have more than one project to reference I think it would blow up the whole solution? And If I commit the references to the repository all team members are affected I think. – koalabruder Oct 09 '12 at 08:50
  • I have this same Q. Also see [Get class source code instead of Metadata in Visual Studio](http://stackoverflow.com/q/7853900/590956) – Sam Dec 06 '12 at 18:08
  • Possible duplicate of [Visual Studio: Debugging a referenced DLL, I have source in another SLN](http://stackoverflow.com/questions/16546703/visual-studio-debugging-a-referenced-dll-i-have-source-in-another-sln) – Fenton Jan 06 '16 at 13:00

1 Answers1

0

This situation only happens in non-Debug modes. It's better to run both in Debug when you are going to debug and set breakpoints.

Run both in the Debug mode.

Seyed Parsa Neshaei
  • 3,470
  • 18
  • 30