Figure out nuget packaging with project references (or a way to make the analyzer assembly accessible to those who reference the nuget package)
Open
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Good place to start- documentation for defining .nuspec properties in .csproj.
https://github.com/NuGet/Home/wiki/Adding-nuget-pack-as-a-msbuild-target
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
Start with the linked NuGet wiki page on defining .nuspec properties in .csproj, then inspect the repository's project and packaging configuration. Determine how the analyzer assembly should be made accessible to consumers referencing the NuGet package, and consider the work complete when project references can use that assembly through the package.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- build-system, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100