microsoft / microsoft/winget-cli
Microsoft.Management.Deployment.Projection should be included in Microsoft.WindowsPackageManager.ComInterop NuGet
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 26.4k
- Forks
- 1.8k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 15
Description
Description of the new feature / enhancement
Microsoft.Management.Deployment.Projection should be included in Microsoft.WindowsPackageManager.ComInterop NuGet.
Currently when using Microsoft.WindowsPackageManager.ComInterop in a C# project you need to manually copy multiple c# files from Microsoft.Management.Deployment.Projection. Ideally this logic should be included in the nuget that it can simply be consumed with minimal to no boilerplate code involved in consuming the API.
Proposed technical implementation details
Microsoft.Management.Deployment.Projection should be included in Microsoft.WindowsPackageManager.ComInterop NuGet.
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 inspecting the Microsoft.Management.Deployment.Projection directory and the Microsoft.WindowsPackageManager.ComInterop NuGet packaging configuration. Confirm how the projection's C# files are currently consumed, then verify that the published package includes them and can be used without manual file copying.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- api, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100