Provide symbol packages (.snupkg) for Kerberos.NET and related NuGet packages
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
Research direction
No files or tests are named. Start by locating the package-generation and publishing configuration for Kerberos.NET and Kerberos.NET.PortableDns, then verify that each release produces .snupkg files containing usable symbols for debugger source stepping.
Written by the indexing model from the issue text.
Description
Is your feature request related to a problem? Please describe.
I love being able to build on top of Kerberos.NET by simply adding a NuGet package to my project, but if I run into a Kerberos error related to the way I'm using the library, I can't debug down into Kerberos.NET code to see what I'm doing wrong.
Describe the solution you'd like
I would love to have .snupkg symbol packages for Kerberos.NET and Kerberos.NET.PortableDns so that I can walk through the code in the debugger and see where I have maybe not supplied the right configuration or parameters in using the library.
Describe alternatives you've considered
My workaround for now has been to write a quick test application project directly in the Kerberos.NET source where I have cloned the repository. This works well, but takes time and could potentially go awry if my quick test application doesn't represent my main project well.
Additional context
Maybe debug symbols are available another way that I'm not aware of.
- Dominant language
- C#
- Stars
- 567
- Forks
- 109
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from dotnet/Kerberos.NET
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
dotnet/Kerberos.NET#394 ·
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 48/100
dotnet/Kerberos.NET#435 · 4 reactions ·
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 72/100
dotnet/Kerberos.NET#434 · 4 reactions ·
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 42/100
dotnet/Kerberos.NET#433 ·
-
enhancement
Difficulty 3/5 1-2 days Newbie friendliness 66/100
dotnet/Kerberos.NET#428 · 8 comments ·
All issues in dotnet/Kerberos.NET
Similar issues
-
[Feat] 조합 영역 구분선 개선 Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
type/automation type/tech-debt
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
t/bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
ci-failure-cause test-failure
Difficulty 2/5 1-3 hours Newbie friendliness 82/100