Reputation: 1871
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?
Upvotes: 4
Views: 2230
Reputation: 5430
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
Microsoft.SourceLink.Vsts.Git
to your project - the one which will be dotnet pack
later (as of now in preview - make sure you tick "Include prereleases" in VS Nuget Manager)<AllowedOutputExtensionsInPackageBuildOutputFolder>$(AllowedOutputExtensionsInPackageBuildOutputFolder);.pdb</AllowedOutputExtensionsInPackageBuildOutputFolder>
into PropertyGroup
where the TargetFramework
element is..NET Core
task with command pack
The nuget package will now contain PDB files so you clients can easily debug your library.
Upvotes: 1
Reputation: 56944
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
Upvotes: 1
Reputation: 59037
You can publish your symbols to a file share. There is not presently support for using VSTS itself as a symbol server.
Upvotes: 5