No symbols have been loaded for this document - Answer anyone?

[sho_nuff]

Looking for the be all end all answer to this issue.

1) Yes, i'm running in the Debug mode and not in Release
2) Yes, the timestamp on my pdb and dll file are in sync
3) Yes, i'm tried deleting my project and fetching our source tree
again
4) Yes, the Module window shows that all symbols are loaded when
running in the debugger
5) Yes, i'm rebooted.
6) Yes, i've deleted my bin and obj folders, restarted, and tried
again.
Anyone?

SN

[Tom Porterfield]

sho_nuff wrote:

Looking for the be all end all answer to this issue.

1) Yes, i'm running in the Debug mode and not in Release
2) Yes, the timestamp on my pdb and dll file are in sync
3) Yes, i'm tried deleting my project and fetching our source tree
again
4) Yes, the Module window shows that all symbols are loaded when
running in the debugger
5) Yes, i'm rebooted.
6) Yes, i've deleted my bin and obj folders, restarted, and tried
again.

What type of application is this? Are there multiple projects in the
solution? What type of app is your startup project? Have you tried using
multiple startup projects? What type document in what project is generating
the error?
--
Tom Porterfield
MS-MVP MCE
http://support.telop.org

Please post all follow-ups to the newsgroup only.

[Wentu]

Hi all

After passing 1 day on the problem i think i found the definitiv
solution to the "no symbols loaded" problem. I want to share this wit
the whole world, i don't want anyone else wasting a day in this stupi
way.

Here is the situation , in short:
one solution
two projects, the first one (A) calls the second (B) as a .dll .
Both are projects for PocketPC (Smart device applications).
When i set a Breakpoint in the code of B it looks OK but when i Debug
Question Mark appears with the infamous

note: The Breakpoint will not currently be hit. No Symbols have bee
loaded for this document.

The B.pdb has a timestamp different from B.dll and THIS is th
problem.
You have to DELETE B.pdb NOT ONLY from the Debug/bin directory becaus
THERE IS ANOTHER COPY of this B.pdb in the

obj directory and you CAN'T touch this copy so easily. So here is th
complete walkthrough:

1) For your project set "Generate DEBUG information" to FALSE
2) DELETE ALL the occurences of B.pdb under /bin and /obj
3) Set "Generate DEBUG information" back to TRUE
4) BUILD
Between 2 and 3 I also built once but i think this is not necessary.

Now my pdb and dll have the same timestamp and all is workin
perfectly

Bye

JW Emilian

--
WentuPosted from http://www.pcreview.co.uk/ newsgroup acces

[tamer.yousef]

I fixed my similar situation by uninstalling the assemply from the GAC.
It was trying to look for the PDB file there and now after removing it,
it look for the file in the local project.