Publish Symbol Data
You can use your build process based on Default Template to publish the symbol data in your PDB files to a SymStore symbol store. If you publish this data, your team can debug with IntelliTrace. For more information, see Debugging Code Faster by Reviewing its History with IntelliTrace.
Prepare your SymStore symbol store
Before you can publish your symbols by using your build process, your team must first prepare a SymStore symbol store:
To prepare your SymStore symbol store
Set up a folder in which to store the symbols on a file-sharing server (for example, \\contoso-share\symbols).
Grant Full Control permissions to the user account under which the build agent is running.
For more information about build agents, see Create and Work with Build Agents.
Publish symbol data by using a Default Template build definition
You can control whether and how your build process publishes symbol data. You can specify the settings when you edit the build definition, and you can also override these settings when you queue the build.
To publish symbol data by using a Default Template build definition
In Team Explorer:
If you are not already connected to the team project that you want to work in, then connect to the team project.
Choose Home, and then choose Builds.
Open the shortcut menu of a build, and then:
Choose Edit Build Definition, and then in the build definition window choose the Process tab.
Choose Queue New Build, and then on the Queue Build dialog box, choose the Parameters tab.
Under the Basic node, expand the Source and Symbol Server Settings node.
Set Index Sources to True.
In Path to Publish Symbols, type the UNC file path to the folder (for example, \\contoso-share\symbols).
Publish symbol data by using a custom build process template
For more information, see Team Foundation Build Activities: Work with Symbol Data.
For more information
For more information about SymStore symbol stores, see the following topics on the Microsoft website:
For more information about Default Template build definitions, see Define a Build Process that is Based on the Default Template.