Adding support for SymbolSource for both NuGet and MyGet #42
Conversation
|
|
|
Nice! I didn't think it would be this easy when I started looking into it for @warrenbuckley but it is! |
|
HOW DO YOU KNOW THIS STUFF???? |
|
I've no idea! |
|
@Jeavon I'll merge this in... quick check, do I need to register on symbolsource.org? (For any reason?) |
|
No you don't need to sign up, they hooked up with MS/NuGet. You can if you want to see stats etc... You have to add your NuGet API key. The MyGet packages on Symbolsource are also hooked up and you will already have a login/password which is the same as your MyGet log in. https://www.symbolsource.org/MyGet/ As far as I've been able to tell you can't join up a NuGet and MyGet accounts on SymbolSource, you just end up with the same one twice, once for /MyGet and one for /Public |
|
OK cool - so, so far you've only added this for the MyGet deploy right? |
Adding support for SymbolSource for both NuGet and MyGet
|
NuGet is fully automated due to the hook up with MS, so this will work for both now |
|
Groovy, all merged in! Thanks again @Jeavon! #h5yr |
|
Just grabbed the artefacts and they both look perfect, the magic of NuGet! |
This will cause the build scripts to generate both a .nupkg and a symbols.nupkg.
The nupkg will contain exactly the same contents as it does currently, the symbols.nupkg will additionally contain the pdb file and all cs files, this package will be automatically pushed to symbolsource.org (no config needed) and Visual Studio will be able to debug if set to use symbol servers!