Hi,
First of all, if you are using the “Release” build of the modules, please try building the modules or application under “Debug” build.
During debugging session, did the Breakpoint show any warning message on it? If yes, you can get some clues from it. If the debugger cannot load the DLL’s .PDB file, we also cannot step into the source code. The PDB files are debug symbols that are generated with the modules (EXE/DLL). They hold the necessary information for source code level debugging. The debugger will not load a PDB that does not match the binary being debugged (For more information, see http://msdn.microsoft.com/en-us/library/yd4f8bd1(VS.80).aspx). You can check if the debugger loads this PDB file by the following steps:
1. Start debugging.
2. Click “Debug” menu and then select “Windows” to enter the “Modules” window.
3. Locate your DLL module to see if the PDB file is loaded. If the PDB file is not loaded, you can load it manually by right clicking the DLL module and then select “Load Symbols” option).
You can get more information about debugging by refering to http://blogs.msdn.com/jimgries/pages/visual-studio-debugger-faq.aspx (Section: Breakpoints and other Execution Control).
I look forward to receiving your test results.
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.