What you probably want to do is:  

>**Step *Into* Code** with <kbd>F11</kbd>

Instead of:  

> **Step *Over* Code** with <kbd>F10</kbd>

Stepping into code will move into the next method being called.  Often times this is located in another file but it doesn't have to be by definition.

[![Screenshot][1]][1]


**Further Reading**: 

* [First look at the Visual Studio Debugger][2]
* [Navigate through code with the Visual Studio debugger][3]


  [1]: https://i.stack.imgur.com/Xf4ad.png
  [2]: https://learn.microsoft.com/en-us/visualstudio/debugger/debugger-feature-tour?view=vs-2019
  [3]: https://learn.microsoft.com/en-us/visualstudio/debugger/navigating-through-code-with-the-debugger?view=vs-2019

I'm trying to understand the workflow of a project, and want to instrument on each file that is called. 

I've tried to use definition/reference to set breakpoint manually, but it's a huge project that it might miss something this way.

I've also used the step forward button in Visual Studio but it just jumps to the very next line, which makes it impossible to trace the entire project.

Is there something that you can jump to the next file, instead of the next line? Or is there some other tools that could help me understand the flow of the codes?

How to step forward to next 'file' from a breakpoint in Visual Studio?

Answer