Closed mvacha closed 6 years ago
I thought that those packages will be uploaded to symbolsource.org, which was very slow and unreliable?
You are right that SymbolSource.org is unusable. But the alternative (https://nuget.smbsrc.net) which is made by the same author is working just fine. https://tripleemcoder.com/2015/10/04/moving-to-the-new-symbolsource-engine/. But it doesn't fetch the new packages automatically from Nuget, I believe.
Fixed in 2.0.0-beta.36
All that is necessary is to add
-symbols
to thenuget pack
call and upload the additional.symbols.nupkg
files to Nuget. Then anybody who has symbol server configured in VS can debug the nuget package (step into, breakpoints etc.. works).