microsoft / microsoft/winget-cli
Microsoft.WindowsPackageManager.InProcCom NuGet package incorrectly listed as requiring .NETFramework
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 26.4k
- Forks
- 1.8k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 15
Description
Brief description of your issue
When importing the package into a project via PackageReference, NuGet seems to think that it only supports .NETFramework,Version=v0.0.
NuGet.org similarly does not show native as a supported framework on the Frameworks tab.
I suspect this may be due to the lack of a build/native folder with an appropriate .props or .targets file to reference the included .winmd.
Steps to reproduce
- View NuGet listing for the package and nav to Frameworks tab
- View NuGet package contents: https://nuget.info/packages/Microsoft.WindowsPackageManager.InProcCom/1.8.1911
- Create a C++ project and import via PackageReference
Expected behavior
Package supports native as a target framework.
Actual behavior
Package only supports .NET Framework as a target framework.
Environment
n/a
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.WindowsPackageManager.InProcCom package contents and the suspected build/native location. Check how the included .winmd is referenced for a C++ project using PackageReference, then reproduce the NuGet listing and project behavior. Done means the package is recognized as supporting native rather than only .NETFramework.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100