Scott Dorman

ephemeral segment

  Home  |   Contact  |   Syndication    |   Login
  603 Posts | 10 Stories | 862 Comments | 51 Trackbacks

News


Post Categories

Image Galleries


Microsoft Store


Creative Commons License



Locations of visitors to this page

Subscribers to this feed

TwitterCounter for @sdorman

View blog authority

Add to Technorati Favorites

Windows Live Alerts

AddThis Social Bookmark Button

LinkedIn profile

Community Credit profile

The Code Project

Follow me on Twitter

Get Free Shots from Snap.com

Community Credit Hall of Fame

Get Feedghost

Xobni outlook add-in for your inbox



Support This Site

Tag Cloud


Article Categories

Archives

Post Categories

Image Galleries

We have all had the experience of debugging an application in Visual Studio and run into the problem of not having the debugging symbols or having incorrect symbols. This is particularly true when you need to step into .NET CLR code to track down a problem.

Microsoft maintains a public symbol server that provides symbols for the different Windows operating system versions, MDAC, IIS, ISA, and the .NET Framework. This server is for symbol downloads only and is not browseable. In addition to the Microsoft symbol server, you can create your own local symbol server for your own application on either a network share or your own local machine.

In order to setup a symbol server, open the Options dialog, then open the Debugging node and click Symbols. To use the Microsoft symbol server, enter

http://msdl.microsoft.com/download/symbols

as a new symbol file (.pdb) location by clicking the button and editing the text. You will need to enter a path for the cache directory, which can be either a network share or a local directory.

Once you click the OK button, an End User License Agreement dialog will appear (only if you use the Microsoft public symbol store). Once you click Yes to accept the agreement, the symbols will be automatically downloaded to your local cache.

posted on Wednesday, May 23, 2007 4:21 PM