I have a project in visual studio and I've been successfully debugging it for a few weeks. But now, after some bigger changes to the project, whenever I trace each step with the debugger it stops working when entering a certain class, due to a .pdb file missing for some .dll.

The thing is, I haven't added anything to this particular file and the dll in question has nothing to do with my project or code.

When I make a new file in the same location and I copy paste the same code there, the debugging works and I can follow each line again. So I am quite perplexed why all of a sudden it claims to need some .pdb file, when it clearly doesnt need since it traces well the same code moved to a different class.

What can I do to make visual studio not require that random .pdb file?

From what I researched, checking "Enable Just My Code" in the debugging Options should do the trick, but it's already checked and seems to have no effect on my issue.

CodePudding user response：

So I think I traced my issue to a static constructor on the problematic class, in which I tried to access a extern c method that was temporarily commented out.

Why did it decide to go into a random .pdb file to I guess look for the missing method is a mystery to me. It seems like a Visual Studio bug. When I look for a method in a dll "A" and it's not there, I'd like it to point that out, but instead it went for a random dll "B" and it's .PDB file somewhere else entirely. Weird.