New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PDBs and source should be published on a source server #4683
Comments
|
I've done some research into the current state of symbol servers and publishing to NuGet. It's not great.
That means having a symbol server requires a custom solution. While that is a somewhat interesting project, the focus is on finishing v4.0. So, two proposals come to mind:
Or maybe there is yet a better option that fits in the v4.0 timeframe. |
#2: +1 Without "modern" magic, we still need a way to deliver and consume matching source. |
This probably falls into your custom solution category, but the source code for (what used to be) https://nuget.snbsrc.net is at https://github.com/SymbolSource/SymbolSource. If someone gives me access to a server, I could spend some time trying to setup that project so we would have our own symbol server for native PDBs. That should have the magic technology where you just point VS to that server and you don't have to worry about PDBs and source code. |
Yeah, that code is more than what we'd need. If you want to build a custom solution, take a look at how: https://github.com/SeanCline/PythonSymbols or, we could use Azure blob hosting with a redirect in front like: https://github.com/electron/symbol-server |
The solution would need to do the source code magic as well if I'm going to spend time on it. It isn't clear to me whether those projects do that. |
My understanding is that the "source code magic" is just another executable. This gist was a nice read. However, I thought that |
I had researched this when I setup all those symbol packages over a year ago, and thought that the way to do it was to create the legacy symbols .nupkg, which embedded the source files I think, with that SymbolSource project. I didn't realize that |
The toolset PDBs should be available in an installer so we can more easily get detailed stack traces for bug reports. Either it should come standard in the WiX bundle or be available for milestone releases as a standalone .msi that installs itself wherever the core is installed. For reference, it's about 4MB cabbed for toolset and extension PDBs. See barnson/wix3@fee3e49.
The text was updated successfully, but these errors were encountered: