Unable to debug dll
-
Ok, I'm sure someone out here has a fix for this.... I have a project at work (in VB 2005) which has a couple mutually exclusive .dll's which are loaded at runtime. Occasionally, especialy when I switch which one gets compiled and included in the Debug, the symbols don't get loaded properly for the .dll, which means I am unable to debug anything inside it. Usually, I'm able to get it working without too much effort (though I'm never entirely sure what actually fixes it), but this time, nothing I do seems to fix it. I have tried deleting the file from both the folder the .dll compiles in, and the the folder the scripting copies the folder to for runtime. I have tried Cleaniing the Solution. I have tried doing all the above and rebooting. I have checked the Debug settings: Debug is enabled, Optimizations are not. I have tried loading the .pdb manually, but VB says it doesn't match. And I have tried any number of other supposed fixes that haven't worked. Does anybody else have any ideas on how to get the symbols to load so I can debug? This is getting very irritating, and so far has cost me a day of work for just this one incident. Please help!
-
Ok, I'm sure someone out here has a fix for this.... I have a project at work (in VB 2005) which has a couple mutually exclusive .dll's which are loaded at runtime. Occasionally, especialy when I switch which one gets compiled and included in the Debug, the symbols don't get loaded properly for the .dll, which means I am unable to debug anything inside it. Usually, I'm able to get it working without too much effort (though I'm never entirely sure what actually fixes it), but this time, nothing I do seems to fix it. I have tried deleting the file from both the folder the .dll compiles in, and the the folder the scripting copies the folder to for runtime. I have tried Cleaniing the Solution. I have tried doing all the above and rebooting. I have checked the Debug settings: Debug is enabled, Optimizations are not. I have tried loading the .pdb manually, but VB says it doesn't match. And I have tried any number of other supposed fixes that haven't worked. Does anybody else have any ideas on how to get the symbols to load so I can debug? This is getting very irritating, and so far has cost me a day of work for just this one incident. Please help!
OK, so after trying pretty much everything under the sun, I gave up and decided to just put in a MsgBox where I wanted it to break. Not as useful as an actual Breakpoint, but at least I could check one of the things I was wanting to check. So, I compiled and ran. My MsgBox didn't appear. The application didn't get to the MsgBox line................ .................... .................... .................... ...because it stopped at my Breakpoint. :wtf: Don't you just love Microsoft?