Last post Feb 05, 2013 10:41 PM by Parashuram
Jan 23, 2013 01:19 AM|GregRoberts|LINK
Hi (this started at http://social.msdn.microsoft.com/Forums/en-US/vssetup/thread/ff190818-2fe9-4ca6-a146-59ad3427b851 and i was advised to post here)
I am after help on setting up a http: symbol server for visual studio 2010 use.
Note i mean http://server:80 type of approach
NOT the UNC srv:<UNC path>
Due to Domain trust issues with the remote location (where we would like to run this), a UNC path can't be used, but the http: approach should work within our intranet.
We can NAT the addresses to get to the service and turn off security at the remote end (i.e. this will not be available via the internet, only the intranet)
NB: I am not talking a about a Symbol Proxy Server (with its own cache)
<us - our cache> <==== http:80====> <them - say symstore on same machine A> <-- refs -> <machine B>
The symbols at the remote location have pointers to the the dll / pdbs which live on another server.
So at Machine A we have 500Meg of symbols with references to the actual files on Machine B which has Terrabytes of disk used.
What we DONT want is for the system to "cache" symbols on their side, i.e. crazy to have terrabytes to be duplicated when the server has direct access to the files...
On our side we would cache, to ensure only one download occurred to the remote location.
At the remote location NO caching to occur. Just fetch the files through their UNC paths.
e.g. http://msdn.microsoft.com/en-us/library/windows/hardware/ff558846%28v=vs.85%29.aspx without caching at the SymProxy.
i.e. no virtual root of the Web site file copy
>> I am after this technology ?
Thanks in advance
Feb 05, 2013 10:41 PM|Parashuram|LINK
To setup the symbols in visual studio from an http location follow the following link
Also you can refer to the following links
As per your request to not to cache the symbols, Its not going work.
Reason ===== Local cache is the local directory which will be used to download the symbol from the symbol server to local directory. This is to avoid loading symbols files from the symbol server every time the debugger starts. When the debugger starts symsrv.dll
will copy them into local directory. If you don't do this then it will always contact the symbol server for each pdb file and that will make your debugging so slow that it might hang your application. So it is by design we need to give the local cache path.
To free up the disk space you can delete the symbol files but this will slow the first debug as it will download the latest symbols.