Jim Bennett

Senior Cloud Developer Advocate at Microsoft, Xamarin Certified Developer, author of Xamarin In Action, blogger, speaker, father and lover of beer, whisky and Thai food. Opinions are my own.

  Reading, UK

See me soon at:

NDC London

My book:

Xamarin In Action

My podcast:

The Jim And Tonic Show
The Jim And Tonic Show on iTunes

Contact me:

  Xamarin In Action
  Twitter
  The Jim And Tonic Show
  GitHub
  LinkedIn
  YouTube
  Email
  CV

Since releaseing JimLib onto NuGet, I've been dogfooding it as much as possible for my own development. One area I noticed was lacking was in symbol support - if I wanted to view the inner workings of my classes I had to decompile the source using ReSharper. Not an ideal situation.

Luckily there is a better way. SymbolSource is a free service that hosts symbol and source packages for a huge array of NuGet packages and it's integrated into Visual Studio - if a symbol package is available there then with one click you can navigate the source and even step through the code in the debugger. And if that's not great enough as it is, you can easily create and upload symbol packages right from NuGet with minimal changes. The docs are here but basically you add the pdb files and source to your .nuspec, then let NuGet do the magic for you - it will create 2 .nupack files when you pack with the -symbols flag, one without symbols with the normal name, and one with with an extension of .symbols.nupkg. When publishing there is nothing extra to do - if the .symbols.nupkg package is found it will be uploaded to the SymbolSource server at the same time as the main package is uploaded to NuGet.

Check it out - grab the latest JimLib NuGet package, use it in your app and step into the code.




About the Author

Jim Bennett

Cloud Developer Advocate at Microsoft, Xamarin Certified Developer, blogger, author of Xamarin in Action, speaker, father and lover of beer, whisky and Thai food. Opinions are mine

 

Since releaseing JimLib onto NuGet, I've been dogfooding it as much as possible for my own development. One area I noticed was lacking was in symbol support - if I wanted to view the inner workings of my classes I had to decompile the source using ReSharper. Not an ideal situation.

Luckily there is a better way. SymbolSource is a free service that hosts symbol and source packages for a huge array of NuGet packages and it's integrated into Visual Studio - if a symbol package is available there then with one click you can navigate the source and even step through the code in the debugger. And if that's not great enough as it is, you can easily create and upload symbol packages right from NuGet with minimal changes. The docs are here but basically you add the pdb files and source to your .nuspec, then let NuGet do the magic for you - it will create 2 .nupack files when you pack with the -symbols flag, one without symbols with the normal name, and one with with an extension of .symbols.nupkg. When publishing there is nothing extra to do - if the .symbols.nupkg package is found it will be uploaded to the SymbolSource server at the same time as the main package is uploaded to NuGet.

Check it out - grab the latest JimLib NuGet package, use it in your app and step into the code.