All nuget packages to consist of strong named dll
Open
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 18.4k
- Forks
- 3.7k
- Avg merge
- 5h 8m
- Merged PRs (30d)
- 1
Description
To improve the developer ecosystem all nuget packages should only consist of strong named dll's and the current strong named package should be deprecated on nuget.org.
With this change, any downstream application/library benefits.
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
The issue names NuGet packages and strong-named DLLs but does not identify files, tests, or an entry point. Start by locating the package and build configuration and reviewing the existing strong-named package policy. Done means every NuGet package contains only strong-named DLLs and the current strong-named package is deprecated on nuget.org.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100