Use WinMDs from .NET SDK TFM by default for projection dependencies rather than installed Windows SDK
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- C#
- Stars
- 665
- Forks
- 134
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 32
Description
When the .NET 5 Windows SDK specific TFM is used, the WinMDs can be obtained from the Windows SDK projection package and don't need to rely on that version of the Windows SDK to be also installed.
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
No file, test, or entry point is named. Trace how the .NET 5 Windows SDK-specific TFM resolves projection dependencies and where installed Windows SDK WinMDs are selected; done means the projection package supplies those WinMDs by default without requiring the matching Windows SDK installation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- desktop
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100