Yes, I've seen this previous question here and none of the solutions have worked.
On Visual Studio Community 2019 I was debugging a project that I've been working on for years. I have a common library project, that I've built, that I use on multiple solutions - one web, one exe.
In working on the EXE solution, which is one windows app project + about half a dozen other custom libraries, I was debugging along without issue. Changed a bit of code and then started another debugging cycle and suddenly symbols couldn't be loaded for one of the libraries.
If I look in the output folder, the PDB file for the library IS there. If I look in the Debugging Windows... Modules, the library does NOT show up.
If I load up the web project which also uses this library, it debugs fine and the module shows up in the modules window.
I've tried everything in the thread I've referenced above. I've also tried:
- Build, Clean, rebuild, in all sorts of different orders - the PDB is ALWAYS there.
- Removing and readding references to the project from the EXE
- Creating a whole new solution
- Going to a different PC entirely - one that I knew was working yesterday - grabbing my latest code, and still the same problem.
- Reverting back to several different old branches of code, on BOTH the new machine and the old machine, same issue.
- Installing VS updates
- Repairing VS
- Checking my GAC to make sure there was nothing for these libraries in there
- Played with every project setting I could find
- Cursing and praying to the programming Gods
I have no clue what to do next. Obviously this one specific project is not loading the DLL, but I can't figure out any possible reason why. The only thing that changed between a successful debug and the missing symbols error was me changing a few lines of code and clicking Run again. (And I even removed the code changes and it still failed.)
I just don't understand what could have caused this, for this singular library, on this single solution.