In 1.15, the debugger added support for Source Link and Symbol Server. However, it currently doesn't support either symbol servers or source link endpoints that require authentication.
This feature request tracks adding support for either or both of these. My guess is that we would want to do both at the same time, but I could be wrong.
Manually clone the repo/source repository and add a sourceFileMap entry to your launch.json.
Hey Guys,
I presume this is an issue for private Azure Dev Ops repositories then as I'm getting a 401 when trying.
Correct
@gregg-miskelly thanks for the reply. Is there a spec for this and is it up-for-grabs?
Is this planned out at all for a (near-)future version of VSCode? Maybe a way to provide a local fallback for such scenarios?
@ransagy by 'local fallback' do you mean pointing at a local source file? Local source files should always take precedence over SourceLink -- you want to add a sourceFileMap to your launch.json.
We don't have a timeline for the feature currently. It is not particularly easy to do as we need some sort of cross-platform credential UI to do it right.
Hah, missed that bit of the docs, damn.
I completely understand this is nowhere near easy, Just wanted to gauge if there's any work being done towards it, so that answers both my questions. Thanks!
@ransagy It was a good question, so thanks for asking it. I added a 'Workaround' section above to hopefully make it more obvious.
I guess traditional VS taught me to expect that "where is your source" dialog, hence i assumed it's not implemented.
@gregg-miskelly any news on the this one fella?
Most helpful comment
Correct