Breakpoint does not work, and modules do not load DLL files in VS 2010

I am using VS 2010 Professional [64 bit - Windows 7], and in my solutions I have 3 class library projects and 1 wcf service project. All of these DLLs are referenced in my WPF applications. Over the past year, it worked fine, and I was able to debug all the referenced projects. But since yesterday, debugging does not work all of a sudden.

When I put a breakpoint in a class in a wcf project, it says that breakpoints cannot be affected as the source file is different from .... etc.

When I registered in the window Debug -> Windows ---> Modules, all these project DLLs are not visible and say that the pdb files are not available.

But in the WPF bin \ Debug folder, I have all the reference dlls and their pdb is ther.

What could be the problem?

Even I can not debug the wpf project. To get a breakpoint or debugging point, every time I have to clear a solution or project, recreate it again. Then I can debug the WPF project.

In the case of reference DLLs, I deleted the dll and again added a new compiled dll and copied these pdb files to the exe folder of the wpf project. Still not to use !!!!

I changed the parameters in Debug and Options [disabling and enabling the Just my code options, etc.]. But still it does not work.

This is not only my problem. One of my colleagues also has this problem, we took all the latest solution code from TFS. SO I changed the local code path to a new folder and again took the last code from TFS. Nevertheless, the problem exists!

I can run the application. But debugging doesn't work. In a WPF project, all of these dlls are specified correctly.

Can anybody help us?

+6
source share
1 answer

I think I don’t have enough points for comments to ask for specifics, so this may or may not solve your problem, but I’ll hack it. In addition, there are apparently other issues. Therefore, I will first test them to see if they will help.

This issue was resolved by adding a configuration to tell the program which version of the frame to use during debugging. Why doesn't the VS2010 debugger stop at my breakpoints?

Why is Visual Studio 2008 skipping my breakpoints?

If this does not help, I will give it back.

When I put a breakpoint in a class in a wcf project, it says that breakpoints cannot be affected as the source file is different from .... etc.

Looks like this could be one of the following issues:

  • Remote debugging and Visual Studio don't know where to load characters or are they outdated
  • Need to clean and rebuild (what you seem to be doing)
  • The server on which your WCF service is running does not receive updated DLLs and PDBs. If it is IIS Express, try killing the process between builds.

Also, make sure that you are creating Debug mode, not Release mode. When building Release mode, it will create PDB files, if it tunes to it, which allows you to debug the application, code can also be optimized, which can lead to skipping breakpoints.

+1
source

All Articles