Hello,
Check out this kb article:
HOW TO: Use a Symbol Server with the Visual Studio .NET Debugger
http://support.microsoft.com/?id=319037 one idea is to create an env variable called _NT_SYMBOL_PATH and specify
there the directories where you store your suymbols. in my experience
normally when the symbol is loaded (use the modules window while debugging)
when I step into a new function vs.net asks me where is that file located,
so I can specify where are my files.
Hope this helps,
Cris
[quoted text, click to view] "Bob Altman" <rda@nospam.com> wrote in message
news:%23QlOdB8LFHA.4080@TK2MSFTNGP10.phx.gbl...
> Hi all,
>
> While debugging, I occasionally step into a routine for which source code
> is not available. If this happens to be a routine in a dll for which I do
> have source code and a pdb file, how do I tell the debugger so that it
> displays source lines and symbolic debugging info?
>
> Typically, this happens under a couple of scenarios. The first would be
> if I am running an app that I've deployed to a computer other than the
> development computer. In this case, I always deploy both the exe and dll
> files. When the app dies, I can debug the failure by having VS .Net
> attach to the failed app. At that point, I need to tell the debugger to
> look at some folder on a network drive to find a copy of the current
> source files for debugging.
>
> The other common scenario would be if my managed app, running under the
> debugger, wants to step into a routine in an unmanaged dll. On my
> development machine, I have a single directory where I copy all of the
> unmanaged dll and pdb files that we've developed. This directory is part
> of my PATH variable, so Windows can find the dll at run-time. But, since
> the dll and pdb files have been moved from their original locations, the
> magic that finds source files doesn't work.
>
> TIA (and sorry for the excessively long question ;-)
>
