microsoft / microsoft/winget-cli
.NET Projections for InProc NuGet
Open
Nobody has claimed this yet.
Issue-Feature
- Dominant language
- C++
- Stars
- 26.4k
- Forks
- 1.8k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 15
Description
Relevant area(s)
WinGet CLI
Description of the new feature / enhancement
The Microsoft.WindowsPackageManager.ComInterop NuGet package includes .NET Projections for types but the Microsoft.WindowsPackageManager.InProcCom package does not.
Proposed technical implementation details
No response
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.
Research direction
Start by comparing the Microsoft.WindowsPackageManager.ComInterop and Microsoft.WindowsPackageManager.InProcCom NuGet package definitions and their build or packaging configuration. Trace how .NET projections are included in the former, then identify the relevant tests or package validation; done means the InProcCom package exposes the expected projections without regressing existing consumers.
Written by the indexing model from the issue text.
Assessment
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100