Azure-devops-docs: Source Link works with private repositories

[ctaggart]

I think this page needs some major revision. There is confusion between source indexing and Source Link. For .NET, Source Link is recommended using https://github.com/dotnet/SourceLink/.

This answer isn't correct:

Q: Can I use source indexing on a portable .pdb file created from a .NET Core assembly?
A: No, source indexing is currently not enabled for portable .pdb files because SourceLink doesn't support authenticated source repositories. The workaround at the moment is to configure the build to generate full .pdb files.

It is recommended to use Source Link. Source Link can be used with private repositories. The Visual Studio debugger supports authentication. Authentication to GitHub Enterprise works. Some users are not able to get authentication to TFS to work.

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 8cddddb9-2731-3366-2a76-9089b58d7f96
• Version Independent ID: b34de428-c3d2-14d6-a452-302c68b74c87
• Content: Publish symbols for debugging - Azure Pipelines and TFS
• Content Source: docs/pipelines/artifacts/symbols.md
• Product: devops
• GitHub Login: @steved0x
• Microsoft Alias: amullans

[seangwright]

In researching Source Link over the past year or so I've found the documentation, links and instructions to all be conflicting and confusing.

I realize that Source Link as a product has gone from experiment to fully supported, but the documentation has fallen so far behind that it appears to be leading developers down the wrong path.

Is there any definitive, up to date source for information about how to use Microsoft's technologies together? In this case Source Link and Azure DevOps.

[mikeblakeuk]

Any news on this?

[daghb]

Still no news? Really? Docs are still in error, and no information whatsoever on how to publish .snupkg packages to Artifacts?

[rgwood]

This cost me an hour because I was misled as to whether I could use Source Link with private repos.

@seangwright is 100% correct, I've been unable to get Source Link working for our organization and the confusing documentation is a big part of that.

[seangwright]

I did get SourceLink working in Azure DevOps private repos using DevOps artifacts and Azure AD auth through Visual Studio to download the package source when debugging (so it _is_ possible).

That said, there are tons of different flags, buttons, toggles, and values that need to be entered _just right_ to make everything work.

It's worth it in the end, but it's a log of work and research to wire it up.

I would post my solution here but honestly it would require a very long blog post, or completion of the incomplete documentation on the topic, to explain it correctly.

[ctaggart]

@seangwright 🥳 , glad you got it working with Azure DevOps private repos! Please do jot down some notes here that we can use to update the docs for others. A very long blog post would be amazing! I donated months of my time over several years for this and the docs need a fresh set of eyes.