“Symbols for the module MyLibrary.dll were not loaded”?

Question

I\'m trying to learn Windows Phone dev by making a basic app that provides information about Pokemon. To do this, I\'ve created a portable class library (PokeLib.dll) so it\'s

Answer 1

You can use DotPeek to generate PDB files for the library, then place it in the same folder as your dll. One more option, if the code is open-source, is to clone the repo, add the project to your project, add dependency, set build order and start debugging.

Answer 2

I was having this error when I had an assembly that was in the GAC and Visual Studio was not removing it before compile/debug. I was able to resolve it by removing that library (dll) from the GAC.

//if pokelib.dll contained assembly: PokeLibrary.Pokemon 
//and it showed up in the GAC (c:\windows\assembly\) with that assembly name
gacutil /u PokeLibrary.Pokemon

This resolved the warning condition and allowed me to debug once again.

Answer 3

Make sure you do not have multiple VS windows open, specifically of the same project! :)

Answer 4

I found that the project I was receiving the message about, was being optimized when built.

I went into the projects properties, Compile Tab, Advanced Compile Options... and unchecked the Enable Optimizations checkbox

Answer 5

In Visual Studio I selected Build -> Clean Solution. That got rid of this message

Answer 6

I also faced the same error and in my case the problem was because of web.config transformation file which I wanted to setup other than debug.config.

I had to track a bug using stage branch and therefore I setup the active solution configuration as Stage.

• Go to the property option of your project solution
• Click on Configuration Manager button on top right hand side.
• Now drill down the drop down option active solution configuration and you choose configuration (web) file for your project to act on when you run it.

I had chosen the stage and when I build the project I got this error and because of that debuggers were become inactive.

But when I set the option back to debug, issue got resolved.