Files
octokit.net/docs/debugging-source.md
Nick Floyd 00b89daa23 [maint] Removes the old implementation of sourcelink and uses the newer one present in the .net SDK (#2666)
* reoves the old implemetnation of sourcelink and uses the newer one  present in the .net SDK

* cleans up appveyor

* updates proj with sourcelink props

* adds deterministic build check as well.

* Update docs/debugging-source.md

Co-authored-by: Keegan Campbell <me@kfcampbell.com>

---------

Co-authored-by: Keegan Campbell <me@kfcampbell.com>
2023-02-07 11:14:49 -06:00

31 lines
1.3 KiB
Markdown

# Debugging Octokit Source in your app
As of version 0.6, Octokit supports symbol debugging - this enables you to step
into the Octokit source without having the repository on your local machine.
### Enable Symbol Debugging
To enable this, you need to enable this in VS:
- From the top **Tools** menu, select **Options**
- Select **Debugging** from the left sidebar and expand **General**
Ensure you have checked **Enable source server support**:
![Enable source server support](https://cloud.githubusercontent.com/assets/359239/5388961/31f9b29e-8144-11e4-8c47-08aca6dee697.png)
### How does this actually work?
When you hit a breakpoint in your application, you can step into the
Octokit source code using `F11`. This will retrieve the source file associated
with a specific type, and cache it in your local symbols cache.
![F11 step into symbol](https://cloud.githubusercontent.com/assets/359239/5389259/74600502-8149-11e4-94f7-10dc79a0573f.gif)
You can then set subsequent breakpoints inside the source code, to return to
in the debugging session.
### Acknowledgements
Thanks to Cameron Taggart for the initial implementation and the .NET foundation for ongoing support of [SourceLink](https://github.com/dotnet/sourcelink) which we use to provide source debugging.