microsoft / microsoft/CsWin32

Friendly extension methods are in Windows.Win32 namespace which is not commonly included

Open
#1,549 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C#
Stars
2.5k
Forks
123
Avg merge
1d 3h
Merged PRs (30d)
9

Description

Folks often miss the extension methods for COM interfaces because they land in the Windows.Win32 namespace instead of the sub-namespace matching the COM interface. Put them in the same namespace so they are never overlooked.

Contributor guide

Open the contributing guide

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.

Research direction

Start by locating the source-generator logic that emits friendly extension methods for COM interfaces and see where it assigns the Windows.Win32 namespace. Verify the generated methods move to the sub-namespace matching each COM interface, then check the relevant generator tests or generated output for the expected namespace.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.