Comments
Sort by recent activity
Thanks for the reply Brian.
To add to your point about the pdb's. They not only have to be present they have to be from the same build as the dlls you're profiling. The problem I was seeing is that I had the pdb's yet couldn't get a source code location in Ants. I ran a program called "chkmatch" and that tells you if your pdb has the same signature as your dll. If they are not matching Ants must just ignore the pdb (which it should). Our Configuration Management group had our build pdbs copied from a different location so the signatures didn't match our dlls. Anyway, I got that problem fixed and things are working smoothly.
As a side question here. I noticed that if the source code dialog pops up once and you hit cancel, it doesn't pop up again for the same file unless you shut down Ants and restart. If this happens can you force it to open by a hot key or something? I have had this happen a couple of times. I finally copied all the source from my dev location to where the pdbs expected it. The source code dialog can drive you mad after awhile if you have enough different files to find. [image]
Anyway, thanks again for the reply.
-Jason / comments
Thanks for the reply Brian.
To add to your point about the pdb's. They not only have to be present they have to be from the same build as the dlls you're profiling. The problem I was seeing is that...