publish symbols to Nuget
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
Research direction
Review the repository's NuGet packaging and release setup, then read the linked NuGet symbol-package guidance. Confirm how the package is built and published; done means consumers can obtain a .snupkg debug-symbol package alongside the NuGet package.
Written by the indexing model from the issue text.
Description
Is your feature request related to a problem? Please describe.
When consuming the Nuget, there are no debug-symbols available.
Describe the solution you'd like
c.f. https://learn.microsoft.com/en-us/nuget/create-packages/symbol-packages-snupkg
- Dominant language
- C#
- Stars
- 3
- Forks
- 3
- Avg merge
- 6m
- Merged PRs (30d)
- 1
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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 ZEISS/LibCZI_NET
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
ZEISS/LibCZI_NET#21 · 2 comments ·
All issues in ZEISS/LibCZI_NET
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
ClickHouse/clickhouse-cs#639 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
ifpebj-ti/controle-acesso-veiculos#377 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Money ExploitsOpenS: Untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
project-wayfarer/wayfarer-14#1628 ·
Maintainers usually reply within 3 days
-
:watch: Not Triaged dotnet-target-version
Difficulty 1/5 Under an hour Newbie friendliness 85/100
Maintainers usually reply within 1 day