I can reproduce the issue if the DLL project properties are set as shown below -
Visual Studio debugger will not step into code of a separate project that builds to a dll (within the same solution)
I have two projects in one solution. One compiles into an exe which depends on the other project that compiles into a dll. When I try to step into a function from the dll that is called within the exe code, it skips over it. My pdb file for the dll is copied over to the same directory as my exe and so is the dll. When I go into the modules window of the debugger, it says the dll module is loaded as well as its symbols. I have tried to disable debugging "Just my code" but even this hasn't worked. When I try to set a breakpoint in the function, it says "no symbols have been loaded for this document" and links me to this article:I have two projects in one solution. One compiles into an exe which depends on the other project that compiles into a dll. When I try to step into a function from the dll that is called within the exe code, it skips over it. My pdb file for the dll is copied over to the same directory as my exe and so is the dll. When I go into the modules window of the debugger, it says the dll module is loaded as well as its symbols. I have tried to disable debugging "Just my code" but even this hasn't worked. When I try to set a breakpoint in the function, it says "no symbols have been loaded for this document" and links me to this article. I went to the section for when both the modules and symbols are loaded and tried to resolve all 3 of their suggested problems, and it still didn't work.
Any idea what might be going on?