Make Microsoft.WindowsPackageManager.ComInterop NuGet package compatible with .1 .NET TFM

Open
#6,669 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 2 days

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
55/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
csharp

Research direction

The issue names the Microsoft.WindowsPackageManager.ComInterop NuGet package and the C# project’s TargetFramework setting, but no repository file or test. Start by locating the package project and its target framework configuration, then check how package compatibility is verified. Done means the package supports the reported net11.0-windows10.0.26100.1 target without NU1202.

Written by the indexing model from the issue text.

Description

Area-COM-API Issue-Bug Needs-Triage
Relevant area(s)

WinGet CLI, COM API

Relevant command(s)

No response

Brief description of your issue

Microsoft.WindowsPackageManager.ComInterop NuGet package is incompatible with .NET versions that end with .1. That TFM is required for CsWinRT 3 but also has existed for a while without this NuGet package supporting it. Please make it compatible.

error NU1202: Package Microsoft.WindowsPackageManager.ComInterop 1.29.380 is not compatible with net11.0-windows10.0.26100.1 (.NETCoreApp,Version=v11.0).
Steps to reproduce

Set this in the C# project file

<TargetFramework>net11.0-windows10.0.26100.1</TargetFramework>
Expected behavior

Expect it to work.

Actual behavior

Fails with the aforementioned error.

Environment
winget --info
Windows Package Manager v1.29.380
© 2026 Microsoft. All rights reserved.

Windows: Windows.Desktop v10.0.26320.9876
System Architecture: X64
Package: Microsoft.DesktopAppInstaller v1.29.380.0
Dominant language
C++
Stars
26.6k
Forks
1.8k
Avg merge
3d 10h
Merged PRs (30d)
41

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/winget-cli

All issues in microsoft/winget-cli

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.