Hi,

Using Visual Studio 2008 SP1 running on XP Pro, I could always start a debug session for an application that is configured to load one or more assembiles, and reflect on those assemblies at runtime.  In fact, the main application will load one or more assembiles and call methods within those assemblies.  In the main application's debug session, prior to the main application's loading of an assembly during runtime, I could always open a single or multiple source files *from the solution of one of the assembiles loaded at runtime* so when the satellite assembly is actually loaded, the breakpoint would become active. 

I can no longer do this in Windows 7.  Would anyone know why?  This is crucial to my everyday development, and I hope there is a fix.  While running VS2008 SP1 as administrator, I have tried turning off the firewall for domain and home and private networks, but no luck.  I have also tried placing the .pdb files from the satellite assembly in the 'Debug' folder of the main application and no luck. 

Kind regards,

Dan

---

-DK

The message: "The symbol file <symbol_file>.pdb does not match the module." indicates the pdb file doesn't match with the assembly file.

Please first right click and select symbol load information in the Modules window and check if the path of the PDB file is correct.
Second, make sure if the assembly file path is as you expected.
Third, please verify if the create timestamp of both pdb and dll files are same.

I still can't repro the issue by following the steps as you described. Would you mind post the code where you load the satellite  assembly?

Thanks,
 

Hongye Sun [MSFT]
MSDN Subscriber Support in Forum
If you have any feedback on our support, please contact msdnmg @ microsoft.com

---

Please remember to mark the replies as answers if they help and unmark them if they provide no help.
Welcome to the All-In-One Code Framework! If you have any feedback, please tell us.

Hi Dan,

I couldn't find any known bug about this issue. Could you provide the following information?

1. When debugging in Visual Studio, open [Debug] / [Windows] / [Modules]
2. When the satellite assemblies are loaded, view modules window and check if they are displayed
3. If it is displayed, check its Symbol Status. Is it Symbol Loaded?
4. If it is not symbol loaded, please right click and select symbol load information. Check if the symbol is searched correctly.

Output window for Debug is also a place to check if there is any error message.
Please make sure the assembly and its PDB file are built at the same time stamp.

It will be great if you have repro steps for this issue. Thanks.

---

Please remember to mark the replies as answers if they help and unmark them if they provide no help.
Welcome to the All-In-One Code Framework! If you have any feedback, please tell us.

Hi Hongye,

Thanks for your reply.  Unfortunately, all I see in the Debug > Windows Menu are the following menu items:

Breakpoints
Output
Immediate

Your suggested method would be very helpful, however, VS 2008 SP1 seems to have hidden the Modules menu item from me.  What are your thoughts?

Dan

---

-DK

The menu will only appear after you start debug. You can first set a breakpoint before loading assemblies. When the breakpoint is reached, try open the module window again.

---

Please remember to mark the replies as answers if they help and unmark them if they provide no help.
Welcome to the All-In-One Code Framework! If you have any feedback, please tell us.

Hello again,

During a debug session of the main application, I was able to view the modules window and see that symbols had not been loaded for the assembly in question.  After I stopped the debug session, cleaned the satellite assembly solution, rebuilt satellite assembly solution in Debug configuration, then launched a Debug session of the main application, I navigated to the Modules window again.  Then, I attempted to load the symbol file for the satellite assembly from the known path.  Here is what I received:

"The symbol file <symbol_file>.pdb does not match the module."

What do you think is wrong? 

Thanks for your assistance,

Dan

---

-DK

Hello,

I have also verified that a recent build of the satellite assembly on my Windows 7 machine, when run on XP, will, in fact, break at the breakpoint I set in the main application debug session in Visual Studio 2008 SP1.

Thanks for any assistance,

Dan

---

-DK

The message: "The symbol file <symbol_file>.pdb does not match the module." indicates the pdb file doesn't match with the assembly file.

Please first right click and select symbol load information in the Modules window and check if the path of the PDB file is correct.
Second, make sure if the assembly file path is as you expected.
Third, please verify if the create timestamp of both pdb and dll files are same.

I still can't repro the issue by following the steps as you described. Would you mind post the code where you load the satellite  assembly?

Thanks,
 

Hongye Sun [MSFT]
MSDN Subscriber Support in Forum
If you have any feedback on our support, please contact msdnmg @ microsoft.com

---

Please remember to mark the replies as answers if they help and unmark them if they provide no help.
Welcome to the All-In-One Code Framework! If you have any feedback, please tell us.