I'm currently publishing some NuGets to my VSTS feed. Is there support for VSTS acting as a Symbol Server as well so I can publish my symbol packages?
3 Answers
You can publish your symbols to a file share. There is not presently support for using VSTS itself as a symbol server.

- 57,011
- 13
- 100
- 120
-
4@aoetalks - Be sure to vote on this User Voice item if you are interested in this feature: https://visualstudio.uservoice.com/forums/330519-team-services/suggestions/2564053-treat-tfs-as-an-enterprise-symbol-server – Ed Blankenship May 01 '16 at 15:00
-
And how exactly did you do that? do you have a local server on premise and created the file share?, if so how do you secure your server so only the hosted pool could write to it, or you created a VM in azure? if so how did you added the agent to TS? How do you mange the security so the share is visible only to your team? I'm not being sarcastic, I really want to know, administration and cofiguration wise TS feels like huge step backwards – Juan Zamudio Jul 29 '16 at 02:01
-
1There was a update to the User Voice item, this summer a preview version of a VSTS Symbol service will be available. – Scott Chamberlain Mar 20 '17 at 15:32
It is now possible to use VSTS as a symbol server
I've also written a blog post on how to setup a symbol-server using a VSTS build definition where the symbols are published on a file share. It's actually more as a step-by-step guide on how to publish and expose them via IIS

- 56,135
- 11
- 101
- 154
Checkout Source Link. It is becoming a new standard or at least recommended way.
SourceLink is a language- and source-control agnostic system for providing first-class source debugging experiences for binaries. The goal of the project is to enable anyone building NuGet libraries to provide source debugging for their users with almost no effort. Microsoft libraries, such as .NET Core and Roslyn have enabled SourceLink. SourceLink is supported by Microsoft.
In a case of VSTS Git repository and .Net Core
project
- Add nuget reference of
Microsoft.SourceLink.Vsts.Git
to your project - the one which will bedotnet pack
later (as of now in preview - make sure you tick "Include prereleases" in VS Nuget Manager) - Add
<AllowedOutputExtensionsInPackageBuildOutputFolder>$(AllowedOutputExtensionsInPackageBuildOutputFolder);.pdb</AllowedOutputExtensionsInPackageBuildOutputFolder>
intoPropertyGroup
where theTargetFramework
element is. - Add
.NET Core
task with commandpack
The nuget package will now contain PDB files so you clients can easily debug your library.

- 5,102
- 7
- 44
- 69