Can I add GitHub as a debugger source in Visual Studio?

I use some NuGet packages in my projects, which have their own source publicly available on GitHub ( OrmLite example).

How to configure my repositories as debugger sources in Visual Studio (same as I could configure ReferenceSource for .NET Framework, etc. like here )?

ReSharper is able to decompile DLLs, but I'm more interested in seeing comments that are obviously inaccessible in this way.

Update:

I know about pdb files, but the initial installation was to see the source code when I pressed F12 . For the .NET Framework, which is achieved by simply adding the source code, as I explained earlier

+6
source share
2 answers

What you are looking for is http://symbolsource.org , which is a platform for hosting open source pdb files (debugging).

To use it, you need to upgrade your Visual Studio instance to pull out pdb ( http://www.symbolsource.org/Public/Home/VisualStudio ):

  • Go to Tools โ†’ Options โ†’ Debugger โ†’ General.
    1. Uncheck the box next to "Include only my code (only managed)."
    2. Uncheck the box next to โ€œEnable .NET Framework Initial Step.โ€ Yes, this is misleading, but if you do not, Visual Studio will ignore your server order (see below).
    3. Check the box next to "Enable source server support."
    4. Uncheck "Require source files to match original version"
    5. Go to Tools โ†’ Options โ†’ Debugger โ†’ Symbols.
    6. Select a folder for the local character / source cache.
    7. Add character servers in the section "Character file (.pdb)". Pay attention to the correct order, because some servers may contain characters for the same binaries: with or without sources. We recommend the following setting:

Note. Not every nuget package also uploads symbols to SymbolSource (since this requires an additional publishing step). Therefore, you may need to contact the project developer and ask them to download it, or if the project is open source, you can do it yourself.

+8
source

Use the source code from GitHub by downloading the appropriate VS code projects and add them to your linking solution instead of using binary files.

+1
source

All Articles