Skip to main content

Return to Answer

deleted 42 characters in body
Source Link
user247702
user247702
  • 24.4k
  • 18
  • 116
  • 162

There is a tricky case for that:You can get this message when you are using an activator and the assembly you set the breakpoint into has not been loaded yet. The error message is then confusing. 

The breakpoint will resolve once the activator loads the assembly (assuming the assembly and debug symbols are up to date). A good place to look at is the modules window in the debugging menu. There you should look for the assembly which your file belongs too. First check that the assembly is loaded. Then, from where is it loaded? Then, is the symbols file loaded. Again, where is the symbols file loaded from? Finally check the versions of both.

There is a tricky case for that: when you are using an activator and the assembly you set the breakpoint into has not been loaded yet. The error message is then confusing. The breakpoint will resolve once the activator loads the assembly (assuming the assembly and debug symbols are up to date). A good place to look at is the modules window in the debugging menu. There you should look for the assembly which your file belongs too. First check that the assembly is loaded. Then, from where is it loaded? Then, is the symbols file loaded. Again, where is the symbols file loaded from? Finally check the versions of both.

You can get this message when you are using an activator and the assembly you set the breakpoint into has not been loaded yet. 

The breakpoint will resolve once the activator loads the assembly (assuming the assembly and debug symbols are up to date). A good place to look at is the modules window in the debugging menu. There you should look for the assembly which your file belongs too. First check that the assembly is loaded. Then, from where is it loaded? Then, is the symbols file loaded. Again, where is the symbols file loaded from? Finally check the versions of both.

Post Made Community Wiki by betitall
Source Link
David Burg
David Burg
  • 1.2k
  • 17
  • 14

There is a tricky case for that: when you are using an activator and the assembly you set the breakpoint into has not been loaded yet. The error message is then confusing. The breakpoint will resolve once the activator loads the assembly (assuming the assembly and debug symbols are up to date). A good place to look at is the modules window in the debugging menu. There you should look for the assembly which your file belongs too. First check that the assembly is loaded. Then, from where is it loaded? Then, is the symbols file loaded. Again, where is the symbols file loaded from? Finally check the versions of both.